Skip to content
Comitiva
Language:PT
v0.1.0 is out — a hub for teams is next

Agentic chatfor your whole team.

Connect any LLM — an API key or the CLI you already use — give agents a role and a set of tools, and talk to all of them in one Slack-style chat, with many conversations running at once.

DownloadView on GitHub

v0.1.0 · macOS · Windows · Linux · Free and open source · Apache-2.0

Connections

Any model, one chat.

Bring API keys, or the command-line harnesses you already use with their own login. Each agent picks a connection and a model, and many agents answer at the same time.

APIs

  • Anthropic
  • OpenAI-compatible
  • Google Gemini
  • Ollama

CLI harnesses

  • Claude Code
  • Codex

Tools

  • Local folders
  • Google Drive
  • Any MCP server

Local models through Ollama or LM Studio need no key.

What it does

Everything an agent needs. Nothing it should not have.

Many agents, all at once

Start a conversation while another agent is still working. The sidebar shows who is responding, who needs your approval and what is unread.

  • RResearcherneeds approval
  • WWriterresponding
  • RReviewerresponding
  • OOrganizeridle

Folders, Drive, any MCP server

Give an agent local folders (read, or read and write), your Google Drive, or any MCP server you register and test in the app.

~/notes · read ~/drafts · read & write Google Drive MCP
⌘/CtrlK

Search everything

Jump to an agent, a conversation or any message. Full text, accents ignored.

Know what it costs

Every run's tokens and cost, by connection, agent and model, with your own price corrections and a CSV export.

Attachments

Paste a screenshot or drop text files into a message. Providers that cannot see images get the file name instead, and the composer tells you before you send.

Yours to move

Export a conversation as Markdown. Export agents with their connections and tools as a file — never with keys — and import them elsewhere.

Local-first

Everything stays on your computer in SQLite. Keys live in the OS keychain, never in the database. No account needed.

Made for the keyboard

A shortcut for every command, a native menu, light and dark, English and Português (Brasil).

Permissions

You see and control what agents do with your files.

Every tool call goes through one permission gate in the runner, for API models and CLI harnesses alike. Claude Code and Codex reach your tools through Comitiva, so their writes ask too.

  1. Read

    Reading runs freely

    Inside the agent's folders, listing, reading and searching need no approval.

  2. Write

    Writing asks first

    Anything that changes a file stops the run and asks you inline: Allow, Deny, or Always allow for this agent.

  3. Outside

    Outside is refused

    Paths outside the agent's folders are rejected by the server itself, not only by the UI — symlink escapes included.

Per agent: ask before writes, allow writes, or read-only.

Not a coding tool

Agents for any kind of work.

Nothing in Comitiva assumes Git, repositories or a terminal. Agents research, write, review and organize. Code is just one case — and when you need it, it comes in as an MCP server like any other tool.

  • RResearcher

    Reads a folder of notes and reports the themes that repeat, with quotes.

  • WWriter

    Drafts in your Google Drive from a brief, in your house style.

  • RReviewer

    Checks a draft against a checklist and lists what is missing.

  • OOrganizer

    Sorts a messy folder into a structure you approve, one move at a time.

How it is built

Built to outgrow the desktop.

All LLM execution — adapters, streaming, cancellation, the tool loop, MCP clients, approvals and usage — lives in the runner, a plain Node process with a JSON-lines protocol. Electron is one client of it. The hub will be another.

Hubnext

Phase 8 · a remote Backend

The runner is the product

One process owns execution. Any shell can drive it: the desktop today, a server or a CLI tomorrow.

Local-first

SQLite for everything, the OS keychain for secrets. Without a hub, everything works offline. The hub is optional and syncs.

A shared contract

Entities, message blocks and events are published as JSON Schema, so the TypeScript desktop and the PHP hub speak the same language.

Browse the schemas

What's next

Today, your desktop. Next, your team.

Comitiva starts on your computer and grows into a shared workspace. The desktop stays local-first; the hub is optional.

  1. NowAvailable

    Desktop v0.1.0

    macOS, Windows and Linux. Connections, agents, tools with approvals, attachments, search, usage and cost. Checks for updates on its own.

  2. Phase 8Next

    Hub for teams

    Accounts and workspaces. Agents and conversations synced between desktops, live: two desktops see the same conversation as it streams.

  3. Phase 9Planned

    Web

    The same interface in the browser, served by the hub. Team API keys, and API agents running on the server, so teammates without the desktop can talk to them. An online desktop can run CLI harnesses and local tools on the team's behalf.

  4. Phase 10Planned

    Usage policies

    Limits and concurrency per agent, and fallback: an agent switches connection when it hits a limit.

Three ways to run it

  • DesktopAvailable

    Free and open source. Works fully on your computer, no account.

    Apache-2.0

  • Community hubComing

    The hub, open source, on your own servers. For teams that host their own tools.

    AGPL-3.0

  • Hosted hubComing

    The hub, run by us. Billed by usage.

    app.comitiva.dev

See the full roadmap

Open source, from the runner up.

Read the spec, the architecture decisions and the code. Open an issue, send a pull request, or watch the releases.

Star on GitHubContributingWatch releases

Apache-2.0