Agent Farm / Field notes 03
Keep the workflow you like.
Agent Farm is for switching repeatable setups while staying in Claude Code or Codex. Start with the part of your workflow you want to change.
Find your fit
Three ways to set up work.
Choose the approach that fits your workflow.
| Approach | What you manage | Where you work | A good fit when… |
|---|---|---|---|
| Native configuration | Each harness’s own settings, instructions, and tools. | The native Claude Code or Codex interface. | You prefer to configure each harness directly. |
| Agent FarmYour setups, saved | Named profiles, shared skills, child definitions, and workspace connections. | The native Claude Code or Codex terminal, launched with a generated configuration. | You switch roles or projects and want reusable setups. |
| Omnigent | Agents and persistent, shareable sessions through Omnigent. | Omnigent’s interface for its Claude Code and Codex integrations, with connected web, mobile, and desktop interfaces. | You want a shared session experience across interfaces. |
Based on the Agent Farm README and Omnigent terminal documentation, reviewed September 16, 2026. Interfaces and supported integrations can change.
What Agent Farm owns
Configuration, then launch.
Agent Farm combines your agent definition, selected skills, children, and optional workspace connections into a launch bundle. Claude Code or Codex executes the agent turns and supplies the native tools.
Separate bundles let you launch different configurations in one repository. Use separate worktrees for independent code changes.
A sibling project
Need room for parallel work?
Pane manages visible agent workspaces and terminals. Agent Farm manages the setup you bring to a session. Explore Pane when you want to organize multiple pieces of work side by side.