See and approve what your agents do, with a record you can check.

Each agent session that Ikenga starts shows its permission requests, its live cost and its tool calls. Named seats let you pick a session up again by name, hold it or take it over.

Permission cards work with Claude Code; other engines apply their own rules. Figures an engine does not report show as a dash.

• Permission cards Shipped Since 0.8.3

  When an agent asks to run a tool, the request appears as a card in the Companion, and you allow or deny it.

  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.
  • Holding a tool call until you decide is opt-in for each terminal and off by default.

• Seats Beta Beta since 0.16.1

  Give each agent session a named seat in your project, then resume it, hold it or take it over.

  • New in 0.16.1 and still settling.
  • Figures an engine does not report, such as cost, show as a dash.
  • On an engine that cannot resume after a restart (OpenRouter), a vacant seat is marked not resumable and never silently starts a new session.

• Cost meter Shipped Since 0.8.3

  See what each session costs, live.

  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.

• Tool feed Shipped Since 0.8.3

  See which tools each session calls, as it calls them.

  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.

• Held updates Shipped Since 0.14.0

  An app update that asks for new permissions waits for your review.

• App lock Beta Beta since 0.16.1

  Lock Ikenga when you step away, with a PIN or your passphrase.

  • Work already running keeps running while the app is locked; the lock screen lists it.

Follow the files an agent touches while it works, then review the change in git without leaving the app.

• Change ledger Shipped Since 0.8.3

  See the files each agent changes as it changes them.

  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.

• Git app Beta Beta since 0.2.0

  Review changes, read history and work in branches and worktrees without leaving Ikenga.

  • Can occasionally fail to start when Ikenga is busy booting.

A multi-user server is one Ikenga server that the members of one organisation share. Each person signs in to their own account and works in their own space on it, with their own secrets. Members are trusted with each other, so it is not built to keep untrusted customers apart.

Today you build and run it yourself. It needs a Linux host, where it runs as root under systemd and gives each person their own Unix user. It is not part of the desktop download, and device pairing needs it too. Each feature below is in beta.

• Multi-user server Beta Beta since 0.19.0

  Run one Ikenga server for your team. Each person signs in to their own account and works in their own space on it.

  On a server you build and run yourself.

  • Members of one organisation share the server and are mutually trusted; it is not built for untrusted tenants.
  • Sign-in is by username and password; single sign-on is not available yet.
  • The server needs a Linux host: it runs as root under systemd and gives each person their own Unix user.
  • Not part of the desktop download: you build and deploy the server yourself.

• Device pairing Beta Beta since 0.19.0

  Pair a phone or laptop with a short code. Both screens show the same four-word phrase, and you confirm before the device gets in. Give each device its own access level, and revoke it at any time.

  On a server you build and run yourself.

  • Pairing is covered by automated tests; a check with a real phone over Tailscale is still to come.
  • Behind a reverse proxy such as Caddy or tailscale serve, pairing a phone can fail with a "cookie_rejected" message, because the server sees the proxy's address.

• Permission routing Beta Beta since 0.19.0

  A paired phone or laptop can answer permission requests from the agents in your desktop app. Choose whether those requests are answered on this device only or on any paired device. Each device’s access level caps what it may approve.

  On a server you build and run yourself.

  • Today a paired device can answer permission requests raised by the desktop app. On a multi-user server the routing rules are built and tested, but the server's agent engines do not raise permission requests yet.

• Members and roles Beta Beta since 0.19.0

  Invite people to a project, or to a single artifact, with a role (Owner, Operator, Reviewer or Guest) that limits what they can see and do.

  On a server you build and run yourself.

  • The spend cap is shown but not enforced.
  • Invites are links you copy and send yourself; Ikenga does not send email.
  • Ownership cannot be transferred yet.
  • Work done through a share never uses the owner's secrets.

• Audit log Beta Beta since 0.19.0

  Sign-ins, pairings, grants, revokes, role changes, approvals and dispatches go into a hash-chained log. Verify the chain and export it from Settings or the command line.

  On a server you build and run yourself.

  • Export to external logging tools is not available.
  • Removing only the newest entries from the log may not be detected.

• Per-person secrets Beta Beta since 0.19.0

  Each person on a multi-user server keeps their own secrets, separate from everyone else’s.

  On a server you build and run yourself.

  • Secrets are sealed under a key the server operator holds; a lost key cannot be recreated, so back it up.
  • A secret value can be at most 64 KiB, and one person's store at most 8 MiB; a write past either is refused.
  • There is no command to rotate the server's key yet.

Who can read your data on a server you run

Read the 0.19.0 release notes

Groundwork is a planning skill for Claude Code. It keeps a living plan folder for each piece of work: research, the plan, a decision log, tracking, and a plan board you open in a browser. The folder is plain files in your repository, so your team can review a plan the way it reviews code, and agents read the same decisions you do.

Re-run any action and it adds to the folder; it never overwrites what you wrote. When the plan is ready, orchestrate turns it into a brief for each task and a wave order, or a Claude Code Workflow that fans the work out to one agent per task.

Written for Claude Code.

Learn more about Groundwork

Claude Code has its own controls for organisations. Your admins can deploy managed settings that local settings cannot override. They can decide which MCP servers may run, require single sign-on, and route usage through Amazon Bedrock, Google Cloud or Microsoft Foundry. Ikenga does not replace any of that, and it does not route around it. Ikenga runs your own Claude Code installation with your own sign-in, so the settings your organisation deploys still apply.

What Ikenga adds is the workspace around your agents:

• More than one engine. Claude Code is supported. Codex, OpenRouter and Antigravity are in beta, and OpenCode and Pi are experimental. Each uses your own install, sign-in or key.
• A local-first workspace. Projects, the files your agents make, terminals and agent sessions are kept on your computer. Your engine still sends your prompts to its own model provider. Ikenga itself sends no usage analytics; the engines you run follow their own settings.
• A store with consent. Claude Code has no built-in catalogue of MCP servers. Ngwa, the store, installs skills, tools, hooks and apps from a signed catalogue, where you see what each one can access before it installs. Skills, agents, commands, hooks and tools can also install from a public git source, pinned to the commit you reviewed.
• A vault and seats. Keys stay in a passphrase vault. Named seats keep track of each project's agent sessions, with their cost and permission requests.

Where Claude Code's controls go further today. They enforce policy on every machine in your organisation. Claude's business plans also add single sign-on, plus SCIM and audit logs on Enterprise. Ikenga has no organisation-wide policy for apps and tools yet; we are exploring it. Sign-in with your identity provider is next.

Your MCP policy also covers Ikenga's tools. Ikenga adds the tools it installs to Claude Code's own configuration files, so your allowlists and denylists apply to them. If your admins deploy a fixed set of servers (managed-mcp.json), Claude Code does not load tools installed through Ikenga.

Nothing on this list is available yet. Each line leaves it when it ships.

Next

• Sign in with your identity provider (OpenID Connect).
• Signed installers for macOS and Windows.
• Apps in the browser when you connect to a server.

Exploring

• SCIM provisioning.
• SAML sign-in.
• Sending the audit log to your SIEM.
• A private catalogue for your team.
• Admin policy for the apps and tools people can install.
• A Tasks app for shared work.

The whole app is free and open source. Paid plans pay for support and for help running Ikenga, not for features.

Team and Enterprise are in early access: design partners and a waitlist only. We won't take payment for them or sign a paid contract until our installers are code-signed. We count members, not seats. A member is a person with the Owner or Operator role; Reviewers and time-limited Guests are free. Seats, the named slots for agent sessions, are always free and unlimited.

See plans and prices