Agent Farm / Field notes 01 # A setup for every kind of work. A planner needs different instructions from an implementer. Save those choices once, then take the right setup into your next repository. The toolkit ## Small pieces. Useful together. * ### [Switch profiles](https://getagentfarm.com/configuration#profiles) Choose a saved agent with its own model, instructions, and skills. * ### [Set up interactively](https://github.com/dcouple/agent-farm#install) Let init check prerequisites and install your starting profiles and skills. * ### [Connect a workspace](https://getagentfarm.com/guide#workspaces) Bring a project’s remote or local MCP tools into a launch. * ### [Manage global skills](https://getagentfarm.com/configuration#global-skills) Load a profile’s skills into your native user directory across repositories. * ### [Install configuration plugins](https://getagentfarm.com/configuration#plugins) Share versioned profiles, agents, and skills; detect conflicts with local edits. * ### [Run headlessly](https://getagentfarm.com/configuration#headless) Use headless execution with an initial message for scripted work. * ### [Declare child agents](https://github.com/dcouple/agent-farm/blob/main/CONFIGURATION.md#agents) Choose native delegation or a separately launched process for each child. * ### [Use either harness](https://getagentfarm.com/compare) Launch Claude Code or Codex with the configuration your agent selects. * ### [Inspect before launching](https://getagentfarm.com/configuration#inspect) Preview a profile’s settings, connections, and source files. * ### [Keep repository context](https://github.com/dcouple/agent-farm/blob/main/CONFIGURATION.md#workspaces-and-repositories) Work alongside the repo’s own AGENTS.md, CLAUDE.md, and references. From setup to session ## Four choices. Then you’re in. After `agent-farm init`, launch the interactive picker with `agent-farm`. This illustrated sequence shows the path to a session. 1. 01 / Profile ``` $ agent-farm › planner implementer reviewer ``` ### Pick a profile Choose the worker and playbooks for this job. 2. 02 / Workspace · optional ``` Project tools None › my-project MCP connections included ``` ### Add a workspace Choose project connections when you need them. 3. 03 / Repository ``` Working directory ~/repos/my-app Profile + tools + repo ✓ ``` ### Point at your repo Choose where the agent will read and work on files. 4. 04 / Native session ``` .agent-farm/generated/ instructions · skills · tools Claude Code or Codex → ``` ### Open your terminal Agent Farm builds the bundle and opens the selected native CLI. Illustrative screens. Your installed profiles and workspaces determine the choices shown. Already know your setup? ``` agent-farm run planner --workspace my-project ``` Review the [launch permissions](https://github.com/dcouple/agent-farm/blob/main/docs/operations.md) before your first run. The same worker, more context ## Give the project a toolbox. A repository tells the agent where to work. A workspace supplies named connections to external tools, independently of that folder. Profile + repository ### Work from the repository. * Your selected model and instructions * Selected skills and child agents * Repository files and local context For example: plan a refactor from the code and tests already in the repo. Add a workspace ### Bring project tools along. * Everything in the profile * Your configured issue tracker * Your configured error or analytics tools For example: use a connected tracker and error service to investigate a reported bug. Add your provider’s MCP endpoints and authenticate them first. Agent-defined connections and native global tools can also apply. [Build a workspace configuration](https://getagentfarm.com/configuration#workspace) [Next / Configuration **See what goes into a setup.**](https://getagentfarm.com/configuration)