Is DevThrottle an AI agent?

No. DevThrottle does not write code and is not an agent - it is the control room for the agents you already run. It lines up Claude Code, Codex, and your other tools on one board so you can see what each is doing at a glance and answer them by voice. You bring the agents and their subscriptions; we never charge you for AI tokens.

The app is free forever, and your code never leaves your computer. We host nothing of yours, so it costs us nothing when you use it. Paid plans only cover things that cost us money - unlimited hosted transcription and support. The free version is not a trial and never expires.

Which coding agents does it work with?

It works with the AI coding agents you already use - Claude Code, Codex, Aider, Gemini, and others - across different tools at the same time. You keep your existing agent and subscription; DevThrottle runs and watches them all on one board.

Factory Droid CLI review - Factory coding agent

Factory Droid CLI is Factory's terminal interface for its Droid development-agent platform. It supports interactive REPL sessions, headless execution, session resume and fork, daemon workflows, and custom Droid automation.

Key capabilities

Interactive and headless modes - droid starts the interactive workflow, while droid exec supports single-shot tasks, file prompts, stdin piping, session resume, and CI/CD workflows.

Custom droids and subagents - Factory supports custom droids/subagents, skills, hooks, plugins, custom slash commands, and mixed models.

MCP and enterprise workflow - The CLI includes /mcp and ties into Factory's broader enterprise development-agent platform.

Autonomy level

Level 5 in the broader Factory platform: autonomous enterprise SDLC work with a terminal control surface. CLI-specific behavior still needs empirical DevThrottle testing.

Strengths

Strong headless and CI/CD story
Custom droids/subagents map well to specialist-agent workflows
Enterprise platform context is useful for larger teams

Limitations

Commercial platform, not local-first open source
CLI behavior must be separated from broader Factory platform claims
Hooks moved from .factory/hooks/hooks.json to scope-root hooks.json; old files still work and are archived on next save

Factory Droid CLI

Key capabilities

Autonomy level

Strengths

Limitations

Sources