You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What a session reaches: every feature and setting against its tool
GOD of Agents (one session controlling every session, on any host; PLAN §10) reaches enowX through the command line and its MCP tools alone. This table is the audit of that: each feature and setting of enowX, the command (and MCP tool) that reads it and the one that changes it, whether it works on another host, and what is missing. Keep it up to date when a feature or a setting comes.
Marks: ✅ read and changed by a tool; ◐ partly (what is missing is said); ✗ no tool yet; — not meant for a tool (the app's own look and feel, a page to look at).
Other host:--host H (MCP: host) runs the command on host H through the app (cli.md); "own" means the command has a --host of its own; "synced" means the data is the same on every host already (user-data-sync.md); "app" means the app answers wherever it is asked from.
◐ the current model and effort aren't printed by a tool yet (they are in session.transcript)
Its time budget
✗ session.budget has no command
Private from the host's teams
✗ session.private has no command
Rewind (edit a past message)
✗ session.rewind, the chat's alone
Its slash commands
✗ session.commands has no command (send "/…" types one)
Attach to its terminal
attach
this host
✅
Its tabs, ports, Run menu
ports, run
run N, run --save
this host
◐ no --host
A virtual display (desktop apps on Linux)
display
this host
✅
Its Browser
browser snapshot|screenshot|eval
browser open|click|fill
this host
✅
Pipelines
pipelines
pipeline
this host
◐ cancelling or removing one: no command
Automations
automations
automation add|run|enable|disable|remove
this host
✅
Take over a teammate's session
— the app's, between people
When the user is asked
What can't be undone (the confirm methods in core/hostcontrol: close, push, pull request, merge, discard, removing a project, a host's environment variable, changing what GOA runs on) and hibernating or stopping sessions, asked by an agent, follow the asking session's permission mode:
In bypass, on the user's own hosts: done without asking, and logged: control log says not asked: the agent is in bypassPermissions.
Always allowed, hibernating and closing only: the card for these two offers Always allow, for the session asking. From then on, on the user's own hosts, that session hibernates and closes sessions without a card, each logged: control log says not asked: the user always allows this session, and nothing would be lost. It still asks for an agent at work, something served, an app shown, a program left running, what can't come back on its conversation (a shell, where it can't tell what runs), its own session, and a teammate's session; and for push, pull request, merge, discard, removing a project and a host's environment variables, whatever it was allowed. A teammate's session never gets the choice, and a request to a teammate's shared host always asks. The asking session's daemon holds the rule, in a file that outlives a restart (control-allow.json); the app checks another of the user's hosts' sessions, which only it reaches. Settings → Agents → Always allowed lists the sessions and revokes the choice. It isn't reachable through host.call, but like the rest here it is no boundary against an agent with the host's socket.
Anything else: a card for the user's yes (agents.md, Agents don't move the user), which doesn't take the keyboard. That includes a mode not known, auto, acceptEdits and the like, a teammate's session on this host, and any request to a teammate's shared host, which also keeps checking the role.
The mode comes from the daemon, never from what the session sends (HostCallParams.Bypass is overwritten): what the agent's own hook last reported as permission_mode, which it does just before each tool call, so a shift+tab counts by the next call. A report counts for two minutes, and is forgotten when the agent restarts and when the daemon does. How a session was started counts for nothing, since the mode can change after.
Agent
What enowX knows
Without asking
Claude Code, Claude Agent Teams, OpenClaude
permission_mode in its hooks, bypassPermissions when it asks nothing
Yes
Codex
the same field; bypassPermissions when it never asks for approval
Yes
Every other agent, and any agent on Windows
no report: --yolo at the start says nothing of now
No, always the card
This follows the agent's mode; it isn't a boundary against the agent. A command the agent runs could call enowx hook with a mode of its choosing or name another session in From, as it could already leave From out; agents' other asks (features, the vault, moving project copies) are unchanged.
Review and merge
Feature
Reads
Changes
Other host
A session's branch against its base
changes ID (session_changes)
--host
✅
Its diff
changes ID diff [--files] (session_changes diff)
--host
✅
Commit
changes ID commit -m (session_commit)
--host
✅
Push, pull request, merge, discard
changes ID push|pr|merge|discard --yes (session_push, session_pr, session_merge, session_discard; yes; the user confirms)
goa switch, goa restart (goa_switch, goa_restart, not offered to it)
the user's: Settings in its header, or goa switch / goa restart, which it is refused (goa.md)
--host
— the user's
What a watched GOA did itself
goa flags
reverting: the user's, in the app
this host
— the user's
Built-in skills
goa skill (goa_skill) prints guides that ship in the program, on every host and for any agent, which GOA's prompt points at: setup, doing every setting with the user and stopping for what needs them, and features, every feature from the registry (core/agent.Features), so it can't fall behind. A test checks every command they and the prompt name exists. Decisions' and RAG's settings are reachable: rag settings, rag set, rag project on agreed|off, rag plan, decide settings, decide use, on this host; keys stay typed in the app or named from the vault.
goa doc (goa_doc) prints these docs, which ship in the program too (package docs, every top-level doc but the roadmap, PLAN.md), so a host with no repository has them: the list with a line on each, one doc, a --section, or --search WORDS. It is what GOA answers questions about a feature from, rather than the code.
What GOA can't do yet
Everything below GOA says it can't do, and where the user finds it; it doesn't work around it. In order of use.
What
Where it is today
Follow-up
A session's checks: find and run tests, linters, build
Side panel, checks.list, checks.run
checks command and MCP tools; until then, delegate running them
Review comments on a session's diff
The Git tab
Command to add and send them; until then, send the comments as a prompt
Adding, connecting, removing a host
Hosts page; the list is hosts.json, the password in the keychain
App command through host.call, a password never in the arguments
Removing a project; arranging projects on another host
Project's menu (project.remove through host.call only); projects group|move here only
Command that opens the sign-in for the user; accounts rm
Adding a judge, and typed keys for judges, RAG and PostgreSQL
Settings → Decisions, Settings → RAG
decide add taking a vault credential's name; a typed key stays the app's
RAG's and Decisions' settings on another host
This host's commands only
--host on rag and decide
Token usage: its switch, budgets, prices
Settings (tokens.setSettings, tokens.prices)
usage set, usage budget, usage price
A session's time budget
The chat, New session (session.budget); the default is settings app set time-budget
switch --budget
A session kept private from the host's teams
Its menu (session.private)
switch --private
Rewinding to a past message
The chat (session.rewind)
rewind ID N, for Claude Code and Codex
Listing a session's slash commands
The chat (session.commands); send "/…" types one
commands ID
The model and effort a session runs on, read directly
The chat's header; chat shows them
A line in status
Permission prompts on agents other than Claude Code
answer knows Claude Code's keys only; read the screen and send
Keys per agent in its adapter
Tabs, ports and the Run menu of another host's session
ports, run here only
--host on both
Cancelling or removing a pipeline
A project's pipelines, ⋯ menu
pipeline cancel|rm
Moving or packing a project with its sessions
Copy to host… (transfer.*); project copy copies the files
project copy --sessions
Starting a session from a GitHub issue
New session (project.issues)
spawn --issue N
Setting a server up like this device
Set up… (setup.scan)
setup scan|plan, running in a session
Creating a server at a provider
Hosts → Create a server… (the provider's token)
vps create, the token named from the vault
The daemon's log
Settings (daemon.log)
daemon log, masked
Resource usage of a host
The rail's Resource usage (daemon.stats)
stats
Keeping the app in the tray, looking for updates
Settings → App
Fields in app.settings
Stays the user's, with no follow-up: restarting a daemon; the vault's master password, adding a key and typing one (never in the chat or a command); agreeing to a project's files going to an embedder (rag project on agreed records what they said); the rules for GOA (goa rules reads them); taking over a teammate's session; reverting what a watched GOA did.
The app's own look and feel, with no command planned: the floating control, Discord, the sidebar, the keyboard shortcuts. Theme, accent and terminal font are commands: settings app set, with the app open.