suparagent README

The project's README from github.com/Anil-matcha/suparagent. As one markdown file: README.md.

Suparagent

A workspace for AI coworkers.

Create named agents, give each a job and workspace, and bring them together to complete real tasks. Suparagent keeps conversations, memory, routines, and approvals in one place. Use the desktop app or host the server yourself; the hosted service is a separate product.

Bring your own engine and provider account. Suparagent does not include a model or model subscription.

Desktop downloads · Self-hosting · Hosted app · Watch the demo · Discord

▶ Watch: Free Unlimited Grok Bot Alternative: Open-Source, Any Model, No Restrictions

Status: Suparagent is in active development. Desktop releases, self-hosting, agent computers, and newer team features are still evolving. Review known limitations before relying on them for important work.

Contents

Quick start

The desktop app runs from a source checkout. It needs Node.js 22 or newer, uv, and at least one engine available on the same computer. For a CLI engine, install it and sign in before opening Open Duet. You can also configure an API-based engine in Settings → Engines. Docker is only needed for the optional isolated agent computers.

git clone https://github.com/Anil-matcha/suparagent.git
cd suparagent/desktop
npm run app

On first launch, choose an engine, workspace, and approval mode. Then:

  1. Open Settings → Engines and confirm an engine is ready.
  2. Create an agent with a name, a clear job, and a workspace.
  3. Start a chat. Choose Ask first to pause for approval before actions that need it.
  4. Add teammates or create a routine when you want to split up or repeat work.

See the Releases page for current desktop installers and the changelog for changes. Installers are experimental and unsigned. The assisted update flow offers a SHA-256-verified installer for you to open; it does not install updates automatically. The release-to-release update path has not been verified end to end.

What you can do

A request goes to a Claude or Codex team lead, who delegates work to specialists. Teammates can share a project folder, and you review actions when approval is required.

Ways to run Suparagent

Desktop app Self-hosted server Hosted web app Development checkout
Best for A personal workspace on your computer Keeping your agents and routines available on a server you control Using the separately operated Suparagent service Contributing or changing Suparagent
Where workspace data lives Your computer Your server An account-specific hosted workspace Your development machine or configured database
Start here Quick start Self-hosting guide suparagent.ai Development setup
Main requirements Node.js 22+, uv, and an engine Linux server, HTTPS, Docker or Node.js and uv, and an engine An account and an AI provider account Node.js, uv, and Docker if you use PostgreSQL
Status Experimental Experimental; one owner who can invite teammates Separate hosted product —

The hosted service is separate from the open-source desktop and self-hosted core. Hosted account, workspace, and billing data are handled by Suparagent; see the hosted service's Privacy Policy and Terms.

Hosted plans

The hosted preview lets you use your own Boat key for sandbox compute. Paid plans use compute operated by Suparagent, so you do not need to supply a Boat key. In both cases, you bring your AI provider account and pay that provider for model usage.

Plan Monthly Suparagent price Included running compute Machine disk capacity
Free preview $0 Billed to your Boat account Small profile
Starter $15 100 hours per billing period 51 GB
Standard $49 300 hours per billing period 51 GB
Pro $99 720 hours per billing period 111 GB

Paid-plan compute hours count while the sandbox is running, including idle time. At the limit, it stops until the next billing period or a plan change; compute overages are not charged. The disk value is the selected machine's capacity, not a separate storage quota. A stopped sandbox's disk is subject to the provider's retention period, so export important files before a paid plan ends. Paid checkout is enabled for hosted accounts; see the Suparagent pricing page for current plans.

Engines, data, and costs

Connect an engine you already use: Claude Code or Codex CLI, Gemini CLI, Google Gemini through Antigravity, Cursor, another command-line agent using the Agent Client Protocol (ACP), OpenRouter, or an OpenAI-compatible API such as Ollama or LM Studio. Available tools vary by engine; image input and agent computers, for example, are not supported by every engine. See engine setup and capabilities.

For desktop and self-hosted use, conversations, agent notes, routines, and settings are stored in that instance's local data folder or server database. Workspace files stay in the folders you assign to agents. API keys saved through Suparagent are encrypted there; command-line sign-ins remain with the engine installed on that machine.

When an agent answers, the selected engine receives the prompt and the context needed for that turn. This can include text you attach, relevant notes, and workspace content the engine reads. If the engine is a hosted service, that information is handled under that provider's terms. You bring the provider account, CLI sign-in, or API key; model usage may cost money.

Example: prepare a weekly project briefing

Create a lead agent and specialists, such as a researcher and an editor. Give them the same project workspace, and set the lead's engine to Claude or Codex. Ask the lead to prepare a briefing from the notes and reports in that folder.

The lead can split the request into smaller tasks and hand them to the specialists. Their work runs in separate conversations, then returns to the lead to assemble. Follow along in chat and approve actions when the settings require it. Once the process works well, make it a weekly routine and review each run in the app.

Scheduling tasks

Routines run prompts on local agents on a schedule, by webhook, or on demand. They run in the backend, so the backend must stay running. The original Telegram bot and Boat sandbox task flow are optional and separate from the agent workspace. See backend scheduling details and environment settings.

Known limitations

Guides

Getting started

Agents and work

Tools and customization

Project

Support

Contributing

Issues and pull requests are welcome. Start with the contributing guide.

To propose a third-party app for the in-app MCP Marketplace, add a Community manifest under marketplace/plugins/community/, regenerate marketplace/catalog.json, and submit both in a pull request. See the MCP Marketplace submission guide for the manifest requirements and validation steps.

License

Suparagent is licensed under the Apache License 2.0.

suparagent (Anil-matcha/suparagent)

Searching Database…

What is this?An open-source, self-hosted AI agent workspace and alternative to paid products like OpenAI Dots, Claude Cowork, Grok Bot and ChatGPT agent. The prototype focuses on coding-agent workflows: running Claude Code tasks from Telegram or a browser, reviewing risky actions, and scheduling recurring prompts.
Is this a hosted service I sign up for, or something I run myself?Something you run yourself: a FastAPI backend, a Next.js web UI and an optional Telegram bot, all using the same API, sandbox and per-user credentials.
How do I get it running?Fill in backend/.env, then run ./scripts/dev.sh from the repo root — it starts Postgres via Docker, installs dependencies, runs migrations and launches the API, the Telegram bot and the web UI (Git Bash works on Windows). Ctrl+C stops everything except Postgres.
What do I need before it will actually work?Locally: uv, Node.js 20.9+, Docker for Postgres (or the experimental SQLite mode) and Bash. Account-wise: a 'Boat' API key for sandbox creation, plus Claude linked via its OAuth login — currently the only supported agent. A Telegram bot token is only needed for the bot or linking; the web UI's guest mode works without it.
How rough is it, given the prototype label?Early: the README says 'Prototype / active development' and points to a Known limitations section to read before running it for others. It also states outright that its features differ from the paid services — it is not a feature-for-feature replacement.
How are my tokens and task records stored?Credentials are encrypted with a Fernet key you generate yourself, and sandbox, task, permission and schedule records live in your own PostgreSQL.
Can the agent search the web?Optionally — set PARALLELSEARCHENABLED=true and new Claude tasks get free Parallel web search and page fetching over MCP. No Parallel account or API key is needed, but it's rate-limited for light use and off by default; you approve the tool calls through the usual permission prompts.
Why run this instead of paying for one of those agents?The pitch is an inspectable workspace you control yourself: coding tasks with visible approval steps and local control over the app and its data. The README is upfront that features differ from the paid services rather than matching them one for one.
Does the web UI work without Telegram?Yes — continue as a guest with a local id, no bot needed, and you can link a Telegram identity later by sending /link to the bot. One quirk: schedules created in the browser use your timezone, while Telegram ones are always UTC.
Size
7.3 MB
Stars
7.1K
Updated
CommitNov 17
Age
3y
Commits · 90 Days