Use it
The Code desk
Point it at a project folder. It opens the real files, runs the project's own tests, and remembers what the project decided.
The Code desk is the other side of the app. Open a folder and you get that folder's files, its language server, a terminal and git — the same tools you would use yourself, with a model holding them.
Two modes
| Mode | You | The model |
|---|---|---|
| Agent | Say the job and review the diff | Reads, edits, runs commands and tests, reports back |
| Editor | Write the code yourself | Suggests, explains, and edits only what you ask it to |
A first task worth trying
- Open the folderPress Open Folder on the Code desk, or drop the folder on the window. Nothing is copied or uploaded.
- Ask a question first*"How does this project run its tests?"* — it reads the README and the config, and tells you what it found.
- Then a small change*"Add a test for the empty case in this file and run the suite."* Watch which files it touches.
- Read the resultPass or fail, it says which test failed and what it changed. A failing test is a result, not a failure of the app.
What it remembers per project
Decisions, conventions and the things that went wrong once live with the project, so the next session does not ask again. That memory is separate from the Assistant desk's — a conversation about documents does not fill the prompt of a coding job.
Checks before it says done
- The project's own tests, not a generic linter it brought along.
- The language server's errors, read from the same LSP your editor uses.
- The page it just built, opened in the room and clicked through.
- What it could not check, said out loud rather than left out.
Letting an agent program do the turn
The code desk runs on Aetox's own engine by default. If this machine already has an agent program installed and signed in, Aetox can be its window instead — the bubble, the tool timeline, the Stop button and the transcript stay Aetox's, and the loop belongs to that program.
- Where
- In a code chat, open the engine picker and choose External Adapters — it opens as a full page
- Drivers that exist
- Claude Code · Antigravity · OpenCode · Devin — each row takes a name and a path (empty means it finds the program itself), and the vendor's CLI must be installed and signed in on the machine that runs the engine
- The account
- Belongs to that program. Aetox shows only the kind of account; it neither stores nor sees the key
- Share MCP
- On gives that program Aetox's tools for that turn only · off leaves it with its own tools and its own permissions
- Switching off or deleting
- Off hides it from the engine strip and moves the chats using it back to Aetox · delete removes the profile only, never the program or its account
- A new driver
- Not yet — an unknown driver is refused; what you can add is more profiles of the four that exist