A directional view of where FlareCode is headed. This is not a commitment or a schedule — priorities shift with what beta users actually need. The best way to move something up this list is to open an issue or upvote an existing one.
- Hosted coding agents that take a plain-English task and open a GitHub Pull Request
- Isolated, encrypted sandbox per agent; durable workspace that survives restarts
- Multi-repo per agent + fleet mode (run agents in parallel across repos)
- Auto-pilot (opt-in autonomy) with a hard cost cap on every task
- Bring your own key (Claude, GPT) or bundled inference (Kimi K2.6)
- Live in-browser app preview + in-app terminal
- Self-testing agents (in-container browser + verifiable test runner) gating "done"
- GitHub-native review (branches are always
flarecode/task-*, never your default branch)
- Widening closed-beta access
- Notification polish (Slack, GitHub mobile, email)
- Deploy tiers (preview / publish / production)
- Public developer surface: SDK, CLI, and a reference MCP server
- More model providers
- Native mobile review experience
- Team / organization features
Tell us — feature request or Discussions.