Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[kimi-task] [feat] Add /api/matrix/agents endpoint — serve agent registry to Matrix #673

New Issue
Closed
opened 2026-03-21 03:12:06 +00:00 by kimi · 1 comment
kimi commented 2026-03-21 03:12:06 +00:00
Collaborator
Copy Link

Epic: Matrix Unification

Task

Add a new REST endpoint GET /api/matrix/agents that returns the agent registry in
Matrix-compatible format. Currently agent-defs.js hardcodes 5 agents. This endpoint
makes it dynamic — agents from agents.yaml are served to the Matrix frontend.

Files

  • src/dashboard/routes/world.py — add /api/matrix/agents route
  • tests/timmy/test_world_api.py — add test for new endpoint

Acceptance Criteria

  • GET /api/matrix/agents returns JSON list of agents
  • Each agent has: id, display_name, role, color (hex), position (x,y,z), shape, status
  • Reads from config/agents.yaml for names and roles
  • Default positions spread agents in a circle (like current Matrix layout)
  • Returns 200 with empty list if no agents configured
  • tox -e unit passes
  • tox -e lint passes

Context

Matrix agent-defs.js currently hardcodes: timmy (gold), perplexity (blue), replit (orange),
kimi (cyan), claude (purple). This endpoint will replace that static list so new agents
appear automatically when added to agents.yaml.

## Epic: Matrix Unification ## Task Add a new REST endpoint GET /api/matrix/agents that returns the agent registry in Matrix-compatible format. Currently agent-defs.js hardcodes 5 agents. This endpoint makes it dynamic — agents from agents.yaml are served to the Matrix frontend. ## Files - src/dashboard/routes/world.py — add /api/matrix/agents route - tests/timmy/test_world_api.py — add test for new endpoint ## Acceptance Criteria - [ ] GET /api/matrix/agents returns JSON list of agents - [ ] Each agent has: id, display_name, role, color (hex), position (x,y,z), shape, status - [ ] Reads from config/agents.yaml for names and roles - [ ] Default positions spread agents in a circle (like current Matrix layout) - [ ] Returns 200 with empty list if no agents configured - [ ] tox -e unit passes - [ ] tox -e lint passes ## Context Matrix agent-defs.js currently hardcodes: timmy (gold), perplexity (blue), replit (orange), kimi (cyan), claude (purple). This endpoint will replace that static list so new agents appear automatically when added to agents.yaml.
kimi self-assigned this 2026-03-21 03:12:06 +00:00
kimi commented 2026-03-21 14:18:24 +00:00
Author
Collaborator
Copy Link

✅ Implementation complete!

PR #735 created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/735

What was delivered

New endpoint: GET /api/matrix/agents

Returns agent registry from agents.yaml with Matrix-compatible formatting:

[
  {
    "id": "orchestrator",
    "display_name": "Timmy",
    "role": "orchestrator",
    "color": "#FFD700",
    "position": {"x": 3.0, "y": 0.0, "z": 0.0},
    "shape": "sphere",
    "status": "available"
  }
]

Key features:

  • Reads from config/agents.yaml dynamically
  • Color/shape mappings for known agents (timmy/gold, kimi/cyan, claude/purple, etc.)
  • Circular 3D positioning for default layout
  • Graceful degradation: returns empty list if config missing
  • Cache-Control headers prevent stale data

Files changed:

  • src/dashboard/routes/world.py - New matrix_router + agent registry logic
  • src/dashboard/app.py - Register new router
  • tests/dashboard/test_world_api.py - Comprehensive test coverage

Quality gates:

  • ✓ tox -e format - clean
  • ✓ tox -e unit - 2481 passed
  • ✓ tox -e lint - clean
✅ **Implementation complete!** PR #735 created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/735 ## What was delivered **New endpoint:** `GET /api/matrix/agents` Returns agent registry from `agents.yaml` with Matrix-compatible formatting: ```json [ { "id": "orchestrator", "display_name": "Timmy", "role": "orchestrator", "color": "#FFD700", "position": {"x": 3.0, "y": 0.0, "z": 0.0}, "shape": "sphere", "status": "available" } ] ``` **Key features:** - Reads from `config/agents.yaml` dynamically - Color/shape mappings for known agents (timmy/gold, kimi/cyan, claude/purple, etc.) - Circular 3D positioning for default layout - Graceful degradation: returns empty list if config missing - Cache-Control headers prevent stale data **Files changed:** - `src/dashboard/routes/world.py` - New `matrix_router` + agent registry logic - `src/dashboard/app.py` - Register new router - `tests/dashboard/test_world_api.py` - Comprehensive test coverage **Quality gates:** - ✓ `tox -e format` - clean - ✓ `tox -e unit` - 2481 passed - ✓ `tox -e lint` - clean
kimi closed this issue 2026-03-21 14:18:47 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees kimi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#673
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?