The Archive · Android · Guides
Start a Code session
Connect the bridge, open a coding session that runs on the phone, choose its model, and follow its commands, approvals and changes.
Checked on Android 0.1.38
A newer version is out (Android 0.1.40): some details may differ.
Code is the coding agent, and it runs on the phone: sessions open on the device, commands run in a sandboxed terminal on the device, and the files it reads and writes are the phone’s. No computer has to be awake.
Before the first session
Section titled “Before the first session”The terminal of a Code session runs every command through the bridge — the same one Settings → Phone control pairs. With the bridge down, no terminal and no command can start, and Code tells you so when you open it, with a way to Settings. Connect TALOS to the phone first; after a phone restart, reconnect it.
Start a session
Section titled “Start a session”- Open Code from the menu.
- Tap New, or simply write below: the first message starts the session.
Sessions are listed by date — today, yesterday, the last 7 and 30 days — each with its state: Running, Waiting for approval, Interrupted or Concluded with an error. A session can be renamed or deleted from its actions; deleting removes it from the phone for good.
Choose the model
Section titled “Choose the model”Each session has its own model and provider: any OpenRouter model, or OpenAI, DeepSeek or Ollama directly. Anthropic and Gemini are recognized and refused with that reason, rather than pretending to work. A model on the phone cannot drive a Code session yet: choosing one is refused, not left to fail halfway through an answer.
Follow the work
Section titled “Follow the work”- Commands run on the phone, shown in plain words before they run; their output comes back into the conversation.
- Approvals are per tool, not per session: reading a file and deleting one are separate decisions.
- Tool calls collapse into groups, with a diff for each file changed.
- Long conversations are compacted, and you see it happen.
- Delegation: a session can hand a self-contained sub-task to a child agent that starts with nothing but the instruction it was given.
Close the app and come back: the session is where you left it, with the model it was using and what it was waiting for.
If it does not start
Section titled “If it does not start”- “TALOS is not connected to this phone” — the bridge is down: turn on wireless debugging, then reconnect from Settings → Phone control.
- “Code couldn’t start its terminal on this phone” — close and reopen TALOS; that usually fixes it.
- “Session not found” — the session no longer exists; go back to Code and choose one from the list.