ENGINES
Two engines, one workspace.
Choose Claude Code or Codex for each session. Both use the same interface.
Choose an engine when you start a session.
Open-source agent workspace
One workspace for Claude Code and Codex
Shared connections, memory, and skills. Run on your computer or a cloud server. Add extensions for your workflow.
C
Claude CodeAnthropic · Your subscription
O
CodexOpenAI · Your subscription
LaptopmacOS · Linux · Windows
ServerDocker · VPS · Tailscale
PhoneSimple mode · Push
The shared layer keeps connections, memory, and skills on your laptop or cloud server. Use your phone for remote access.
Motivation
Bundling an engine with an app ties your workspace to a vendor. Changing engines should not mean starting over.
Your connections, memory, and skills belong to you. Keep them in one workspace, whether you choose Claude Code or Codex.
Agents run on a real computer, locally or in the cloud. They pause for passwords and payments. Use Take over to complete these steps yourself.
Build extensions from the chat as your workflow changes. Add what you need without waiting for a release.
SHARED
Same connections, memory, and skills.
Both engines use the shared layer for connections, memory, skills, and MCP tools. The exception is claude.ai connectors, which are Claude-only.
Manage connections in Settings.
MACHINE
Your computer or the cloud.
Each agent has its own desktop running in the background. At a password or payment step, it pauses. Use Take over to complete the step on its screen.
Get a notification on your phone and use Take over to enter the password.
Agent desktop
Your approvalSESSION
Your session, in tabs.
Keep chat, code changes, the team board, a live browser, artifacts, and extensions in one window. Review code with Approve and Merge.
One session: Changes, a published artifact and a browser open as tabs next to the chat.
EXTENSIONS
Extensions for your workflow.
Ask in the chat for an invoice tab, an approval gate before Merge, or a webhook. Extensions load in seconds without a restart.
The diagram shows four extension types: tab, Merge gate, listener, and tool.
youBuild an invoice tab with a form that sends a prompt to this session.
Tab
Merge gate
Listener
Tool
Loads in seconds · no restart · in your repo
ORG
Control plane preview.
A separate service in pilot and preview. Each employee gets an isolated Arigami instance through the company IdP using OIDC. Updates run only when sessions are idle. Each instance has full backup and restore.
The diagram shows company sign-in and separate employee instances.
Employeesigns in with the company IdP
Control planeorg bundle · reconcile · backup
Personal Arigamia namespace per employee
dana.arigamiupdates between turns · rollback
roi.arigamiupdates between turns · rollback
noa.arigamiupdates between turns · rollback
+
More capabilities
1
Human approval
Review an approval card before a message is sent or code is merged.
2
Parallel sessions
A manager session starts child sessions to work in parallel in git worktrees.
3
Persistent agents
Give each agent a name, personality, memory, allowlist, and daily budget.
4
Scheduled and triggered
Cron, webhooks, and listeners start sessions even when the browser is closed.
04 / Install
Two ways to install
Download the desktop app, or use one prompt to install on a server or with Docker.
1
Desktop app
version 0.5.1Download and open the app. It signs you into the cockpit automatically, without a pairing code.
Requires Claude Code or Codex installed and authenticated on your computer.
Desktop builds are unsigned. macOS and Windows show a warning on first launch. Approve it once. GitHub releases
2
Server or Docker
Paste one prompt into Claude Code on the machine that will run Arigami.
Install Arigami on this machine using the official instructions: https://github.com/maor700/arigami/blob/master/docs/INSTALL.md Choose the documented setup for this machine. Follow docs/DOCKER.md if using Docker. Show me the cockpit URL and pairing code when it is ready. Let me enter the code and connect my account myself.
Open the cockpit, enter the pairing code, and connect an account for the engine you want to use.
Dependencies installed automaticallyBun ≥ 1.2git + ghClaude Code CLI
For phone access, use Tailscale or your own HTTPS proxy. The cockpit itself listens on loopback.
Installation docs05 / Security
Security and control
Agents run with your permissions. Treat the cockpit as an admin console.
Local access only
The cockpit listens on 127.0.0.1. For remote access, use Tailscale or your own HTTPS proxy.
Enter passwords yourself
The agent pauses at password, 2FA, and payment steps. Use Take over to complete them on its screen. Passwords do not pass through the chat or the model.
Approvals across engines
Permission cards and allowlists work with Claude Code or Codex. Codex has no local sandbox. The claude.ai connectors are Claude-only.
Telemetry off
Telemetry is off by default. Arigami does not collect your prompts, file paths, or usage data.
06 / Source
Stored as files. Open source.
Each agent is a folder. Skills are Markdown files. Memory lives in plain files on your disk. Arigami is released under Apache-2.0.
$ARIGAMI_DIR/ ├── agents/ │ └── kesher/ │ ├── agent.json │ ├── persona.md │ └── memory/ ├── skills/<name>/SKILL.md ├── memory/ │ ├── USER.md │ └── MEMORY.md ├── triggers.json └── state.json