What Aria can do with each agent

Implemented, not yet verified end to end

• Approvals in Aria

  Claude Code and Codex are the two agents where you can allow or deny a request from Aria.

  Claude Code Approvals

  Aria sees its activity from logs and hooks, replays hook sessions on your Mac, and answers approval requests through hooks you connect. Headless launch and resume are built.

  Codex Approvals

  The same as Claude Code: logs and hooks for activity, local replay for hook sessions, approvals through hooks you connect, and headless launch and resume.

  Connecting is a button you press in Aria; nothing is written to your agent’s settings until you do. An approval can be answered only when an installed hook delivered a live request that is still pending. A log line saying an agent is waiting does not give Aria permission to answer it.

  What is not verified: live allow and deny continuation. The hook reply path is implemented, but I have not confirmed end to end, on a live session, that the agent carries on correctly after Aria answers. Launch and resume also still need live verification.

• Observe only

  Gemini CLI, Cursor and Copilot CLI are shown in Aria, but Aria cannot answer their approval prompts. You approve in the agent itself.

  Gemini CLI Observe only

  Aria reads its current session files and an older JSON format. Tested against fixtures. Shows a limited timeline. Launch and resume arguments are tested against fixtures; I have not run the real CLI through them.

  Cursor Observe only

  Aria reads a coarse transcript, and a live check is still pending. It can propose a launch or resume in ask mode with the sandbox on. Edits would need a blanket bypass that Aria never turns on.

  Copilot CLI Observe only

  Aria reads its events file, tested against fixtures; the real CLI’s format has not been accepted yet. Launch and resume use scoped read and write access with the shell denied. The CLI is not installed on my test Mac, so it has not been run.

• Activity only

  OpenCode, Aider, Amp, Cline, Goose, Roo and any command-line agent name you add.

  Aria guesses that they are working from the processes running on your Mac. There is no replay and no approval. It can interrupt a process it knows is running, jump to its terminal, and copy a handoff to your clipboard. It cannot launch or resume them.

• Good to know

  Signing in to a provider stays in that provider’s own tool. Aria never holds your login.

  Interrupting needs a known running process; Aria cannot promise it for an agent it only sees in a log. Team approvals add a suggestion and handoff layer, and the Mac that started the request still runs its own safety checks before anything is applied.

  This is not a compatibility guarantee. A fresh-account and second-Mac run has not been done.

Something here wrong for your setup? Tell me through support. The full list of what is read is on What Aria reads.