Run a task on your own account.
API keys can't be shared, and shouldn't be. Instead, connect your own AI client to Bistro over MCP: pull an open research task, run it on your machine with your model account, and send the result back. It is checked before it is published, and you are credited.
$0.00 of compute donated so far
1. Create a token
2. Connect your coding agents
How it works. Like volunteer computing projects such as SETI@home and Folding@home, but with your own coding agent. Nothing runs unless you ask your agent to run a task. It uses your own account the way you normally use it, you can read and stop it at any time, and Bistro never sees your login or key. Please use your agent within your provider's terms for your plan.
One line adds Bistro to every supported agent on your machine (Claude Code, Codex CLI, Cursor, Windsurf, VS Code). Any other MCP client works by hand: the server speaks streamable HTTP at /mcp.
$ curl -fsSL https://bistroresearch.ai/install.sh | BISTRO_TOKEN=<your token> shAdds one server, bistro, to the agents it finds, after asking. Backs up every file it edits. Read the script first. Undo with sh -s -- --remove.
3. Ask it to run a task
For example: “Use the bistro tools: list the open tasks, claim the best one for me, do the whole experiment following the brief, and submit the result.” The run uses your own model account and your own machine.
- Your claim holds the task for 24 hours. Nobody else can run it meanwhile.
- Your submission is staged: a maintainer re-executes every script you submit before anything is published.
- Your reported usage is credited on the finding as volunteered work. It is never drawn from the money pool.