Command Palette

Search for a command to run...

UnylyUnyly
Весь каталог

Gimmecores

БесплатноНе проверен

Run builds, tests, Docker containers and AI-agent jobs on your other computers on the local network, only after their owner says yes. Sandboxed, with limits the

GitHubEmbed

Описание

Run builds, tests, Docker containers and AI-agent jobs on your other computers on the local network, only after their owner says yes. Sandboxed, with limits the owner sets. macOS, Linux, Windows.

README

Borrow the CPU and memory of computers next to you, with their owner's consent.

Website · Download · Install · Where it fits · AI agents · Documentation · Security

GimmeCores lets a developer run builds, tests, scripts, Python and Docker containers on another machine on the same Wi-Fi/LAN or connected by a Thunderbolt/USB4/Ethernet cable. Work is bundled into tasks, sent to a peer whose owner granted access, and the results come back. GPU lending is planned (design); today it lends CPU and memory.

The command is gimmecores, with the short alias gmc used throughout these docs.

Where it fits

  • Idle computers lying around. A spare Mac or Linux machine becomes extra cores for builds, test suites and batch jobs. From Python, pool.map() spreads the work over every computer that granted you resources (Python SDK).
  • A room full of people. Colleagues you trust can lend each other idle machines for heavy builds and test runs. Each owner approves the request, sets the limits and can stop it.
  • AI agents that need more compute. Coding agents connect through the MCP server (gmc mcp) and run jobs on your other computers, several at a time. They can never ask for or approve access.
  • Your own Docker image, over there. When the owner allows it, gmc run --image sends your image; only the layers the other computer lacks travel, and it is removed when your grants end (container images).

Status: early development (M1, branch v1). Pairing, grants, remote runs, the audit log and laptop protections work end to end between two daemons on one machine over loopback, and Windows borrowing from Linux works between two virtual machines on one Mac. Paired devices find each other on the local network (mDNS). Tasks run in a container (real Docker, tested on macOS and in Linux CI) or in the OS sandbox (Seatbelt on macOS, bubblewrap on Linux), each with its own attack tests. Not yet verified: two physical machines over Wi-Fi or a cable. Approvals (pairing, accepting a request, turning lending on) are checked by the daemon with Touch ID / your password on macOS, polkit on Linux, and Windows Hello / your Windows password on Windows; the macOS prompt has been checked by hand and the Windows ones in a Windows 11 VM, the Linux one not yet. On Windows this version borrows only: lending a Windows PC is refused until it is tested on a real PC (Windows). Do not lend to devices you don't fully trust yet. See the roadmap.

Try it (macOS / Linux, from source)

$ cargo build --release            # binaries: target/release/{gmc,gimmecores,gmcd}

# On the machine that lends (container tasks need Docker; `gmc runtimes sandbox` needs none):
$ gmc daemon                       # or gmcd; listens on port 47474
$ gmc lend on                      # lending is off until you turn it on
$ gmc pair                         # prints a ticket and waits

# On the machine that borrows:
$ gmc daemon
$ gmc pair gmc1:…                  # paste the ticket; both screens show the same 6-digit code
$ gmc grants request <lender-name> --cpus 4 --memory 8g --hours 2

# Back on the lender: review and accept
$ gmc requests

# On the borrower, from your project folder:
$ gmc run --image python:3.12-slim --out reports -- python -m pytest

Your own container image. Ask for a grant that lets you send images, and gmc run --image sends yours from this computer's Docker when the lender lacks it. Only the layers it lacks travel, so after a rebuild only the changed ones go. It runs there as locked down as any container: no network, an unprivileged user, a read-only system, hard limits. The lender keeps it under a name of its own, for you only, and removes it when your grants end. See container images.

$ gmc grants request Desktop --runtime container --cpus 6 --memory 12g --images 8g
$ docker build -t myjob:1 .        # on your computer, for the lender's processor
$ gmc run --peer Desktop --image myjob:1 --out results -- python train.py

On macOS the first gmcd start shows a firewall prompt asking to accept incoming network connections: allow it on machines that should lend or pair. Use GMC_HOME=/some/dir to run more than one node on a machine.

Install

macOS app (Apple silicon): once a release is published, install GimmeCores in your Applications folder, from the release's GimmeCores.dmg (drag it onto Applications) or with Homebrew:

brew tap tanuj24/gimmecores https://github.com/tanuj24/gimmecores
brew install --cask gimmecores           # GimmeCores.app in Applications; gmc and gmcd on PATH

It is not signed with an Apple Developer ID yet: the first time, macOS blocks it, and Open Anyway in System Settings > Privacy & Security lets it run. After that it updates itself: Settings > Updates > Check for updates (it goes online only then). Every update must be signed with the GimmeCores update key, which the app checks before replacing itself (how).

Windows 10 and 11 (x64; Windows on ARM through its x64 emulation): once a release is published, run its GimmeCores-<version>-x64-setup.exe. It is not signed yet, so SmartScreen asks once: More info > Run anyway. It installs the app, the background service (started at sign-in from the app) and gmc on the PATH; approvals use Windows Hello, or where it is not set up the Windows password on Windows' secure screen (after Ctrl+Alt+Delete). On Windows this version borrows: it runs your work on your other computers. Lending a Windows PC comes in a later version (gmcd refuses it until it is tested). Details: Windows.

Homebrew from source builds everything on your machine, so there is no pre-built binary for macOS to warn about; brew upgrade updates it, not the app. Use this or the cask, not both. (Linux Homebrew builds are untested.)

brew tap tanuj24/gimmecores https://github.com/tanuj24/gimmecores
brew install --HEAD gimmecores          # gmc, gmcd and (on macOS) GimmeCores.app
brew services start gimmecores          # or use the app's "Start GimmeCores", not both
brew upgrade --fetch-HEAD gimmecores    # to update later

On macOS, ln -sfn "$(brew --prefix)/opt/gimmecores/GimmeCores.app" ~/Applications/ puts the app in Launchpad and Spotlight. Only one gmcd runs per user: a second one (from another service, or a terminal) says so and exits.

Without Homebrew:

  • macOS: ./packaging/macos/build-app.sh builds dist/GimmeCores.app (and a .dmg). Open it and click Start GimmeCores: gmcd then runs in the background and starts at login (turn that off in the app). Install under "This computer" puts gmc on your PATH. The build is ad-hoc signed, so other Macs will warn until it is signed with a Developer ID.
  • Linux (Debian/Ubuntu): packaging/linux/build-deb.sh builds dist/gimmecores_<version>_<arch>.deb with the desktop app, gmcd, gmc, gimmecores, the polkit policy used for approvals and a systemd user unit (not enabled). Install it with sudo apt install ./dist/gimmecores_*.deb, then open GimmeCores and click Start GimmeCores (or systemctl --user enable --now gmcd). GMC_NO_DESKTOP=1 builds it without the app (servers, Raspberry Pi).
  • Linux, any distribution: cargo build --release && packaging/linux/install.sh --enable installs into ~/.local/bin with a systemd user service, and offers to install the polkit policy. The sandbox runtime needs bubblewrap.

Desktop app (macOS, Linux, Windows)

A window and a menu-bar (tray) icon for everything that needs your consent. Requests to use your computer (accept / decline) and pairing codes stay at the top; below them, three views:

  • Activity: every task other devices run on this computer, live: the command (arguments that look like secrets hidden), which device, what it asked for against what it uses (CPU, memory, its folder's size, time), Stop task for one task, and what finished recently and how it ended. Figures that were not measured say so; they are never shown as zero.
  • Devices: each paired device with what it may use here (revoke) and what you may use there; pairing; Trusted mode; unpair.
  • Settings: the lending switch, laptop protections, ways of running tasks, and this computer's options.

It notifies you when a device asks to use your computer. It connects to a running gmcd and never starts it; approvals still go through gmcd's own check (Touch ID, Windows Hello or your password). In a terminal, gmc tasks shows the same live list (--all adds finished tasks, --watch redraws it) and gmc tasks stop <id> stops one task.

$ gmcd                                   # in one terminal
$ cd apps/desktop && cargo run --release # in another

Closing the window keeps the menu-bar icon; quit from its menu.

On macOS, tasks from other devices run as fast as programs you start yourself. While one of them uses every core, your own heavy work shares the cores with it; Pause on battery, Pause when hot and Only while I'm away are your controls. Stopping GimmeCores (the app's switch, brew services stop, logging out) stops every task it was running.

AI agents (MCP)

gmc mcp is a Model Context Protocol server, so an agent (Claude Code, Claude Desktop, other MCP clients) can run test suites, builds and other heavy work on your devices that granted this one resources. Its tools: devices, run, job, jobs, cancel. What it cannot do: ask for or approve access (you and the person at the other device still do that), send folders outside its root, override the secret scan, send environment variables, give tasks network access, or use Trusted mode. Under a grant that lets this device send images, an agent's image is sent from this computer's Docker like gmc run's (images are not secret-scanned). When the agent session ends, its running tasks are stopped.

$ cd ~/code/my-project
$ claude mcp add gimmecores -- gmc mcp --root "$PWD"     # Claude Code

For Claude Desktop (or another client that starts servers itself), give the full path and the project folder:

{ "mcpServers": { "gimmecores": {
    "command": "/opt/homebrew/bin/gmc",
    "args": ["mcp", "--root", "/Users/you/code/my-project"] } } }

The root defaults to the folder the server starts in; your home folder and / are refused. Agents that can already run shell commands can also simply use gmc run. Any agent that runs on your computer and can start a local (stdio) MCP server can use it. From each vendor's documentation (November 2026; only Claude Code is exercised here, and the SDK tests use the official MCP client):

Agent How to add gmc mcp
Claude Code claude mcp add gimmecores -- gmc mcp --root "$PWD"
Claude Desktop claude_desktop_config.json (Settings > Developer > Edit Config), as above
OpenAI Codex CLI, ChatGPT desktop app (its Codex) codex mcp add gimmecores -- gmc mcp --root "$PWD", or [mcp_servers.gimmecores] with command and args in ~/.codex/config.toml
OpenAI Agents SDK MCPServerStdio(params={"command": "gmc", "args": ["mcp", "--root", path]})
Gemini CLI mcpServers in .gemini/settings.json (command, args)
Cursor mcpServers in .cursor/mcp.json ("type": "stdio")
VS Code (GitHub Copilot) code --add-mcp '{"name":"gimmecores","type":"stdio","command":"gmc","args":["mcp","--root","/abs/path"]}'
Windsurf / Devin Desktop, Zed, Cline, goose their MCP settings: a command server with gmc and mcp --root <folder>

Apps that are not on your computer cannot use it: ChatGPT on the web, claude.ai and OpenAI's Responses API only reach MCP servers on the internet, and GimmeCores stays on your local network. Apps started from the Dock or Start menu do not get your shell's PATH or folder, so give them the full path of gmc and an absolute --root.

How it works

$ gmc pair                      # both screens show the same 6-digit code; both confirm
$ gmc grants request "Desktop" --cpus 8 --memory 16g --hours 4
  (the desktop's owner sees exactly what is asked and accepts, edits or declines)
$ gmc run -- pytest -n 8        # runs on the desktop, logs stream back
import gimmecores as gmc

@gmc.task(cpus=2, memory="4g")
def render(frame: int) -> dict: ...

if __name__ == "__main__":
    with gmc.Pool() as pool:
        results = pool.map(render, range(500))

Trust and security first

Lending your machine is a big deal. GimmeCores is built so that:

  • Nothing runs without consent. Lending is off by default. Every use needs a grant the owner accepted, with limits on CPU, RAM, disk, network and time.
  • The lender enforces the limits, not the borrower.
  • Jobs are sandboxed in containers with no access to the owner's files and no network by default. A container can run, and read, any Docker image on the lender; the approval says so.
  • Everything is encrypted and authenticated device-to-device; pairing defeats impostors on the same Wi-Fi.
  • One click stops everything. Revoking ends running jobs within seconds.
  • Your apps come first. By default, borrowed tasks use what your own apps leave (gmc speed or Settings: full speed, your apps first, or background); a faster level needs you present. See task speed.
  • Everything is logged on both machines.
  • Your device's identity stays put. Its key is an owner-only file; on macOS you can move it into your login Keychain (gmcd --identity-store keychain), where other programs get a Keychain prompt instead of the key. That is opt-in for now: until releases are signed, macOS asks again after every upgrade of gmcd.
  • We say what we cannot protect. For example: a lender can see the code and data you send it.

Read the full threat model.

What GimmeCores is not

It does not make another machine's RAM or GPU appear as part of yours to arbitrary programs — the network is 10–1000× too slow for that (about 10× for Thunderbolt 5 RDMA, 60× for Thunderbolt networking, 1000× for Wi-Fi). It moves work to where the resources are. See feasibility.

Documentation

Contributing and security

Licence

Apache License 2.0.

from github.com/tanuj24/gimmecores

Установка Gimmecores

У этого сервера нет опубликованного пакета — он собирается из исходников. Открой репозиторий и следуй инструкции в README.

▸ github.com/tanuj24/gimmecores

FAQ

Gimmecores MCP бесплатный?

Да, Gimmecores MCP бесплатный — установка в пару кликов через Unyly без оплаты.

Нужен ли API-ключ для Gimmecores?

Нет, Gimmecores работает без API-ключей и переменных окружения.

Gimmecores — hosted или self-hosted?

Self-hosted: сервер запускается локально на твоей машине командой из раздела установки.

Как установить Gimmecores в Claude Desktop, Claude Code или Cursor?

Открой Gimmecores на unyly.org, выбери вкладку своего клиента (Claude Desktop, Claude Code, Cursor) и нажми Install — конфиг сгенерируется автоматически, без правки JSON.

Похожие MCP

Compare Gimmecores with

Не уверен что выбрать?

Найди свой стек за 60 секунд

Автор?

Embed-бейдж для README

Похожее

Все в категории development