AOZUMI Agents overview
AOZUMI Agents runs coding agents for you. You talk to them in Hachi, the Mac app. A thread runs on your Mac with your own tools, or in a cloud agent on AOZUMI that keeps going after you close the laptop.
Local and cloud threads
| Local thread | Cloud thread | |
|---|---|---|
| Runs on | Your Mac, with the Claude Code or Codex CLI you have installed | A cloud agent: an isolated Linux sandbox on AOZUMI |
| Keeps working when the Mac sleeps | Only with cloud standby | Yes |
| Needs | Nothing from AOZUMI | An AOZUMI workspace in the beta |
| Counts against | Nothing | Your plan's agent hours |
A thread can move. Teleport to Cloud sends a local thread to a cloud agent, and Teleport to Local brings it back. The folder on your Mac is left as it was.
How cloud agents work
- One sandbox per agent. Each cloud agent is its own machine with a shell, your repository and whatever tools it installs.
- One agent per project. Cloud threads in a project run in that project's agent. Each thread gets its own folder and works on its own
room/<name>branch, so threads never share a checkout. To use a separate agent, pick one in the composer, or New agent…. - Asleep when idle. AOZUMI stops an idle agent and keeps its files and history. Your next message wakes it; a cold start takes about 20 to 30 seconds.
- Your repository, read only. Agents clone public repositories directly and private ones through AOZUMI, without a GitHub credential in the sandbox. Changes go back as a draft pull request. See Repositories and pull requests.
Codex and Claude Code
- Codex (the default)
- Sign in with ChatGPT inside the agent, or use your workspace's OpenAI API key.
- Claude Code
- In the cloud, only with your workspace's Anthropic API key. Claude.ai subscription logins are never used.
Workspace model keys are shared by every agent in the workspace and stored encrypted; see Model keys. Hachi never copies a login from your Mac on its own. It offers Use your Codex login from this Mac and Add as workspace key, and sends nothing until you agree.
Who can use it
Local agents are open to everyone with a Mac that runs Hachi.
Cloud agents are in a private beta, by invite. Until your workspace is in, the Agents item in the Cloud console's sidebar carries a Beta tag and the page shows a waitlist. See Get access.
Where to manage agents
- Hachi
- Threads, and Settings › Cloud agents: your agents, model keys, plan and agent hours left.
- Cloud console
- Agents in the sidebar, at aozumi.dev/console?view=agents: create, start, stop and delete agents, and add model keys. Open Hachi opens the web app.
- Hachi on the web
- agents.aozumi.dev/chat runs cloud threads in a browser. Local threads need the Mac app.
Next steps
- Install Hachi and sign in.
- Create a cloud agent and check your plan's limits.
- Turn on cloud standby so work continues when your Mac sleeps.
- Open a dev server running in a cloud agent.
Questions
- Is each cloud agent isolated?
- Yes. Each cloud agent has its own sandbox, a Linux machine with a shell, your repository and any tools it installs. Sandboxes are never shared between agents or between workspaces.
- What happens when a cloud agent is idle?
- AOZUMI stops it after your plan's idle time, 10 to 45 minutes, or after two hours if background jobs are still running. Its files and history are kept, and the next message wakes it.
- Can I use my Claude subscription in a cloud agent?
- No. Anthropic does not allow other products to reuse Claude.ai logins. Claude Code runs in the cloud only with an Anthropic API key added as a workspace model key. Codex works with a ChatGPT sign-in or an OpenAI API key.
- Do I need an invite for local agents?
- No. Local threads run the CLIs already on your Mac and need no AOZUMI account. Cloud agents need an AOZUMI workspace with access to the private beta.
Checked against the product on .