Forge Platform

Channel agent catalog

Maintained matrix of channel agent ids in forge-agents. Batch workcells are listed in the workcell catalog.

Updated

Active agents

agent id Package Matrix prefix Autonomy Status
communication packages/communication/ !comm A0_assisted KB + store + Matrix bot
cursor_bridge packages/cursor_bridge/ !agent A1_supervised Matrix adapter + Cursor worker

Stub agents (packaging only)

agent id Package stub Notes
hermes packaging/stubs/hermes.package.yaml Operator assistant — no runtime in forge-agents
openclaw packaging/stubs/openclaw.package.yaml External gateway reference only
factory_droid packaging/stubs/factory_droid.package.yaml Dark Factory placeholder

Stubs provide agent.package.v1 manifests and Dockerfile templates for future Fleet registration. They do not ship runnable code in the A07 track.


communication

Property Value
Purpose Deterministic KB answers for FI + Platform + Blueprints
Ingress Matrix !comm in #communication
Store 30-day SQLite (forge.communication_interaction.v1)
Fleet template forge_agents_communication
Detail Communication agent

cursor_bridge

Property Value
Purpose Headless Cursor agents from Matrix (!agent new)
Ingress Matrix #cursor room; optional NATS bus
Contracts forge.chat_intent.v1, forge.agent_event.v1
Fleet template forge_agents_cursor_bridge (container optional; laptop fallback)
Detail Agent communication guide

Commands: !agent new, !agent list, !agent send, !agent cancel, !agent status, !agent help.


Adding a new channel agent

  1. Add package under packages/<id>/
  2. Create agent.package.v1 manifest
  3. Add Dockerfile template under packages/packaging/docker/templates/
  4. Register row in this catalog
  5. Extend orchestrator registry defaults
  6. Update Platform schema samples if new envelope types are introduced

Do not add batch runners here — use forge-workcells and the workcell catalog.