How-to · 30 Oct
How-to · 3 min read
How to control what an AI coding agent changes on Android
You want an AI agent to work on a real project from your phone, but you worry about it running commands or rewriting files while you look away. On a laptop you would watch the diff, keep a terminal open and stop it the moment something looks off. On a small screen, in a train or between meetings, that kind of supervision is harder. You need clear limits on what the agent may touch, a way to approve risky steps, and an easy way back when a run goes wrong.
- Published
- 17 Nov 2026
- Delivery
- No. 12
- Topic
- AI and agents
- Evidence
- 9 claims quoted from its GitHub page
01
Why it's hard
Most AI coding tools assume you are sitting at a desktop with an editor, version control and plenty of screen space to review changes. Agents that can run shell commands are useful precisely because they act on their own, and that is also what makes them risky when you only glance at them now and then. Costs are another blind spot: a long run with a large model can burn through API credit without any obvious warning. And on a phone, a mistake you do not notice right away can sit in your project until you are back at a computer. So people either avoid agents on mobile entirely or give them full access and hope for the best.
This part describes the usual way. It makes no claims about Rivet, so nothing is quoted here.
02
How Rivet does it
Rivet is an Android app that runs an AI coding agent on a project folder you pick, and it gives you several dials for how much freedom the agent gets. Ask mode asks before every action, Basic YOLO lets small things run on their own, and YOLO runs without prompts. Before risky steps it sets checkpoints, and you can undo a whole run from the Work tab. You can also set spend caps per run and per month so a long task cannot quietly run up your provider bill. You can switch provider, model or thinking level in the middle of a chat if a cheaper model is enough.
Three modes: Ask (asks before everything), Basic YOLO (small stuff runs on its own), YOLO (no prompts).Quoted from its GitHub page
Checkpoints before risky steps. Undo a whole run from the Work tab.Quoted from its GitHub page
Spend caps per run and per month, if you want them.Quoted from its GitHub page
03
Step by step
- 1Install the APK and add your own key from a provider such as OpenAI, Anthropic, Gemini or OpenRouter.
- 2Pick one project folder; the agent only touches files inside it.
- 3Start in Ask mode so every file edit and command waits for your approval.
- 4Set a spend cap per run and per month before you hand over a bigger task.
- 5If a run goes the wrong way, open the Work tab and undo the whole run from its checkpoint.
04
Tips
Keep the project in Git anyway. Rivet's undo restores a run, but the README is clear that it is not a backup, so commit before you start a larger change.
Undo is not a backup. Keep your project in Git or copied somewhere safe.Quoted from its GitHub page
Read commands before you approve them. They run like any normal app on your phone, without a sandbox, so a command that deletes files will really delete them.
Commands run like a normal app on your phone. There is no sandbox. Read what you approve.Quoted from its GitHub page
Write your rules down once. Rivet reads an AGENTS.md file in the project, so instructions like "never touch the migrations folder" or "run the tests before finishing" apply every session without retyping them.
Reads AGENTS.md in your project, so your rules stick.Quoted from its GitHub page
Move up the modes slowly. Stay in Ask while you learn how the agent behaves on your codebase, switch to Basic YOLO for routine edits, and keep full YOLO for throwaway projects where a bad run costs you nothing.
General advice. Not a claim about the product.
05
Questions
Can the agent change files outside the folder I pick?
No. Rivet only works in the project folder you choose, though it can change any file inside it.
Rivet only touches the folder you pick. It can change files in it.Quoted from its GitHub page
Is there a size limit for files it can edit?
Yes. Text edits work on files up to 1 MB.
Text edits work on files up to 1 MB.Quoted from its GitHub page
What happens if I close the app during a run?
The run can continue. Runs keep going in the background with a notification, and if the app is killed a run can resume where it stopped.
Kill the app and a run can resume where it stopped.Quoted from its GitHub page