A desktop app for Factory Droid
AgentVera opens the droid command in a real terminal. Model and effort are given through a separate settings file on every run, and the role is appended to Droid’s system prompt.
Droid in AgentVera
- Command
droid- Install
npm i -g @factory/cli- Sign-in
- Droid uses its own Factory login; if you’re signed out, the agent’s terminal asks you to sign in at launch.
- Model
- Left empty, Droid’s default model is used; the model is passed through a per-run settings file.
- Effort
- Low, medium, high, extra high and max.
- Role
- The role is appended to Droid’s system prompt (--append-system-prompt) and given again on every launch.
- Session resume
- Droid writes its session file once the conversation starts; AgentVera finds it and returns to that session with --resume next time.
- MCP and browser
- AgentVera’s MCP servers aren’t passed to Droid.
What every agent gets
Side-by-side panes
The agent opens in the same grid as the project’s other agents; the layout is remembered per project.
Flows
When the agent finishes a turn, its reply goes through a template to another agent; turn limits stop loops.
Automatic code review
When a turn ends, the code it wrote is reviewed by the Claude model you pick, with findings linked to file:line.
Telegram notifications
Finished turns, errors and flows waiting for approval reach your phone; reply to message the agent.
Queue and broadcast
Queue a message while the agent is busy, or send one message to the agents you pick.
Picks up where it left off
An agent that has received a message returns to its conversation when the app reopens.
Questions
Can each Droid agent use a different model?
Yes. Model and effort are passed through a separate settings file for every run.
How does a Droid session continue?
After the first reply the session file is matched; on the next launch the agent returns to the same session with --resume.
Other agents
All agentsBring your Droid agents into one window.
Download AgentVera, add a project folder and pick Droid under New agent.