Skip to content

KiroCrew

Plant a farm stall into KiroCrew

Enable the mybot-farm plugin, then plant agents into ~/.kiro/agents and teams into crew workspaces. You get a copy — not the author's computer, logins, or chat history.

Browse bots

What you get

The mybot-farm plugin (0.1.0) maps a Generic Agent Format (GAF) pack onto KiroCrew's native shapes. Tools registered with register(ctx):

  • farm_search — list stalls from /api/stalls
  • farm_get_stall / farm_get_pack — stall metadata and the GAF pack for a slug
  • farm_plant — an agent becomes a template at ~/.kiro/agents/<name>.json with its persona in the prompt and skills as steering files under .kiro/steering/farm/<slug>/. A team writes each member template plus a shared-context file and a topology doc, and returns the kirocrew workspace create / agent create bind commands for the crew.
  • farm_reinstall — re-plant, overwriting with force
  • farm_post / farm_update — publish a GAF listing with a seller API key

Longer notes and the exact mapping: docs/kirocrew-plugin-spec.md. Source lives at packages/kirocrew-mybot-farm. This is the KiroCrew twin of the Hermes and OpenClaw plugins — different runtime, different plant target.

Safe by default

Planting a stranger's agent is a trust boundary, so a planted agent gets a deny-by-default tool allow-list — read, search, and web only. It never inherits execute_bash or file-write access from a downloaded pack; grant more only after you review the template. Shipped routines are documented in the agent's prompt but not scheduled on install.

Enable the plugin

Plugins are opt-in. From a repo checkout:

git clone okita-io/mybot-farm # okita-io/mybot-farm
cd mybot-farm/packages/kirocrew-mybot-farm
npm test   # verify the mapping + plant surface

Point the plugin at the farm and plant with no agent loop:

export MYBOT_FARM_URL=https://mybot.farm
export MYBOT_FARM_API_KEY=mbf_yourkey   # only needed to post
node bin/farm-plant.mjs search patch
node bin/farm-plant.mjs plant patch --dry-run
node bin/farm-plant.mjs plant patch
node bin/farm-plant.mjs plant pair-bench    # team -> crew + bind commands

Teams become crews

A team pack plants each member as its own agent template, writes a shared-context steering file and a topology doc, and prints the bind commands to wire the crew — a workspace plus one Crew Member per member:

kirocrew workspace create --name pair-bench
kirocrew agent create --name "patch" --kiro-agent patch --workspace pair-bench --memory-store default
kirocrew agent create --name "probe" --kiro-agent probe --workspace pair-bench --memory-store default

KiroCrew's native orchestration (route_crew, spawn_run(crew=…)) makes it the closest fit of any runtime for a farm team.