re:factory
remote-factory
A plugin and the factory CLI that turn an idea into a plan, then build the project with a team of agents, verification and a PR
- 75 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The builder writes and changes code in your repository and opens a PR, and `--auto-approve` hands approvals to an agent
- `outer-loop` modes run many agent sessions in a row and spend tokens
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/remote-factoryDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The builder writes and changes code in your repository and opens a PR, and `--auto-approve` hands approvals to an agent
- `outer-loop` modes run many agent sessions in a row and spend tokens
This is third-party code. Review the repository files before installing.
What it does
re:factory is a set of agents and the `factory` CLI that designs and builds a program from a description. `factory ceo "idea" --mode design` starts design mode: three researchers, a strategist who drafts a structured plan, your approval, then a builder, a QA agent and a PR. For an existing repository you add a path and `--focus` with the area to improve. In `design-v2` directors design the number of research directions, strategist perspectives and testers on their own, and the human gets a design document with diagrams in place of a compressed plan, plus a user intent ledger the QA checks against. `create` builds new modes and pipelines, and `outer-loop` evolves workflow topologies with MAP-Elites over benchmarks such as FeatureBench. State is local: per project in `.factory/` and globally in `~/.factory/`. A plugin is available for Claude Code, installed with `/plugin marketplace add akashgit/remote-factory#plugins` and `/plugin install factory@remote-factory`, while the CLI does the heavy lifting.
Who it is for. Developers who want to go from a rough idea to a working repository with a plan, QA and a PR through agents.
Good fit when
- You have a rough idea and want a plan with research and approval before code
- You want to work on one area of an existing repository, such as the auth layer
- You need a new agent workflow, such as a multi-stage PR check
- You want to tune a workflow topology on a benchmark and compare variants
Not a fit when
- You need a quick one-file edit: the process with researchers and a strategist is built for a whole project
- You have no Claude Code or Python 3.11: they are required
- You want to hand decisions to agents without approval: stages have stops for your confirmation, and only `--auto-approve` disables them
Example request
Design a Markdown link checker with Obsidian wikilinks through factory ceo in design mode and show me the plan before buildingLimitations
Python 3.11 or newer, `uv` and an installed, authenticated Claude Code are required. The CLI installs globally with `uv tool install git+https://github.com/akashgit/remote-factory.git`, and the reasons are given in the setup guide. The Claude Code plugin only calls the CLI, so the CLI is still needed. `design-v2` with `--auto-approve` lets the CEO agent give approvals at gates, and the result is best reviewed through the PR. The `outer-loop` benchmark modes spend many tokens and much time and are mostly for research.
How to disable. In Claude Code run `/plugin uninstall factory@remote-factory`, then remove the CLI with `uv tool uninstall` for the factory package. State folders `.factory/` in projects and `~/.factory/` are deleted by hand.
FAQ
Where do I start?
With `factory ceo "your idea" --mode design`. The mode researches the topic, drafts a plan with the strategist and waits for your edits before any code is written.
How is design-v2 different from design?
In `design-v2` directors choose the number of research directions, strategists and testers themselves, and you get a design document with diagrams and an intent ledger in place of a compressed plan.
Where is state stored?
In the project folder `.factory/` and global settings in `~/.factory/`. Adding `.factory/` to `.gitignore` is advised.
How does create mode work?
It builds new modes: it researches existing patterns, writes a spec, gets your approval and implements the workflow definition, SKILL.md, CLI wiring and tests.
Does it work in Codex?
The repository has a Codex plugin manifest and a `.codex-plugin` folder, but Claude Code remains the primary agent and is the stated requirement.
Discussion
No questions or reviews yet.
Related
PluginsCodex Factory runs a complex Codex project as a controlled process: plans, roles, source-bound memory and independent verification
Claude Code plugin with 60 subagents and 62 team presets, plus a browser designer for planning agent teams visually.
AI Builder Club Skills
AI Builder Club — Skills
A Claude Code plugin marketplace to make a repo agent-ready and run compounding agent loops
A template for Claude Code projects: parallel agent swarms, workflow skills, safety hooks and rules in one install.
Evolving Agents, director
Evolving Agents (director)
The director plugin for Claude Code compiles CLAUDE.md and memory into linked team rules and puts them before the agent's plan.
Shared infrastructure for Claude Code, Codex, Antigravity CLI and OpenCode: a task lifecycle, skills and sandboxes.
Comparison with similar tools
Cards that share the main search query, and how they differ.
README in short
The project is presented as a harness for designing and evolving software with agent teams. The description opens with the commands for each mode, then a quick start, the design, design-v2, create, focus and outer-loop modes, plugin installation and the plugin agent list.