Agent Registry¶
Source of truth: ge-ops/master/AGENT-REGISTRY.json (2,219 lines)
Admin UI: GET /api/agents (browser) or GET /api/internal/agents/{id} (executor)
What It Contains¶
Per agent:
- name, role, category, team
- status: active, onboarding, unavailable, inactive
- provider: claude, openai, gemini
- providerModel: specific model ID
- redis_stream: triggers.{name}
- identity_path: path to identity files
- skills: list of capabilities
- communication: who can query whom
Status Values¶
| Status | Meaning | Executor Behavior |
|---|---|---|
active |
Operational | Listens on agent's stream |
onboarding |
Being configured | Listens on stream |
unavailable |
Disabled | Ignores stream |
inactive |
Not in use | Ignores stream |
Setting an agent to unavailable silently stops it from receiving work.
How to Query¶
# From admin-ui (browser): GET /api/agents
# From executor/scripts:
curl http://admin-ui.ge-system.svc.cluster.local/api/internal/agents/urszula
# Direct file read:
python3 -c "import json; r=json.load(open('/home/claude/ge-bootstrap/ge-ops/master/AGENT-REGISTRY.json')); print(r['agents']['urszula']['status'])"
Safety¶
When editing the registry: ONLY change what you intend. Verify status fields weren't accidentally modified: git diff ge-ops/master/AGENT-REGISTRY.json | grep '"status"'