GraphoOS

Agents

Delegate the
busywork.

In GraphoOS 0.5, Agent mode (⌘⇧A) works on the workspace: it reads files, proposes a plan and applies changes with AiloOS in the cloud or EmpoorioLM on your machine. You review the diff. Click the tabs.

How to use the assistant →
⌘⇧A · andromedarunning
you · /mode ask · EmpoorioLM local Give every editor action a shortcut, a menu and a palette entry.

Read src/command.rs, keymaps.toml and AGENTS.md. Touch nothing until the plan is accepted.

plan · 3 steps
  1. 01Read command.rs and the default keymaps.
  2. 02Add secondary_actions() and register it in the palette.
  3. 03cargo test -q · allowed in .graphoos/agent.toml
src/command.rs · +8 −3
Files the agent changed: 1 · Review
- fn palette_only(cmd: &Command) -> bool
+ pub fn secondary_actions(cmd: &Command) -> Vec<Action>
+ vec![Action::Shortcut, Action::Menu, Action::Palette]
run · cargo test -q
$ cargo test -q
running 12 tests
test command::palette ... ok
test command::menu ... ok
Keep Undo 1 file · permissions ask · MCP off

The session

Prompt. Plan.
Diff. Terminal.

◌

Permissions in view

/mode ask, edits, auto or plan. Each category (read, write, run, network, mcp) is set in .graphoos/agent.toml.

⌁

MCP and skills

MCP tools from the project or ~/.ailoos/mcp.toml. Skills in .graphoos/skills/. The model does not invent permissions.

✓

The workspace leads

AGENTS.md, .graphoos/rules.md and memory.md enter the context before every task. Keep and Undo cover what the agent wrote.

Your control

Review every
important step.

Agents speed up the work without hiding it. Review diffs, redirect the plan and decide what gets merged.