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/bark endpoint — HTTP fallback for bark messages #675

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

Epic: Matrix Unification

Task

Add POST /api/matrix/bark endpoint that accepts a visitor message and returns Timmy's bark
response. This is the HTTP fallback for when WebSocket isn't available — the Matrix frontend
can POST a message and get a bark back.

Files

  • src/dashboard/routes/world.py — add /api/matrix/bark route
  • tests/timmy/test_world_api.py — add test

Acceptance Criteria

  • POST /api/matrix/bark accepts JSON {text: str, visitor_id: str}
  • Returns JSON bark message (same format as produce_bark())
  • Uses existing bark/chat engine to generate response
  • Rate-limited to 1 request per 3 seconds per visitor_id
  • Returns 429 if rate limited
  • tox -e unit passes
  • tox -e lint passes

Context

The Matrix chat panel currently shows demo barks. This endpoint connects it to Timmy's real
conversation engine. The bark engine uses conversation grounding and commitment tracking
from the Workshop to make responses feel alive.

## Epic: Matrix Unification ## Task Add POST /api/matrix/bark endpoint that accepts a visitor message and returns Timmy's bark response. This is the HTTP fallback for when WebSocket isn't available — the Matrix frontend can POST a message and get a bark back. ## Files - src/dashboard/routes/world.py — add /api/matrix/bark route - tests/timmy/test_world_api.py — add test ## Acceptance Criteria - [ ] POST /api/matrix/bark accepts JSON {text: str, visitor_id: str} - [ ] Returns JSON bark message (same format as produce_bark()) - [ ] Uses existing bark/chat engine to generate response - [ ] Rate-limited to 1 request per 3 seconds per visitor_id - [ ] Returns 429 if rate limited - [ ] tox -e unit passes - [ ] tox -e lint passes ## Context The Matrix chat panel currently shows demo barks. This endpoint connects it to Timmy's real conversation engine. The bark engine uses conversation grounding and commitment tracking from the Workshop to make responses feel alive.
kimi self-assigned this 2026-03-21 03:12:08 +00:00
kimi commented 2026-03-21 14:31:47 +00:00
Author
Collaborator
Copy Link

✅ PR Created: #737

Implementation Complete

Changes Made

  1. Added POST /api/matrix/bark endpoint to src/dashboard/routes/world.py

    • Accepts JSON {text: str, visitor_id: str}
    • Returns bark message in produce_bark() format
    • Uses existing _generate_bark() for response generation
    • In-memory rate limiting: 1 request per 3 seconds per visitor_id
    • Returns 429 with Retry-After header when rate limited
    • Returns 422 for missing/invalid fields
    • Graceful fallback on LLM errors

  2. Added comprehensive tests to tests/dashboard/test_world_api.py

    • 10 new test cases covering all functionality
    • Validates request requirements, rate limiting, response format, error handling

Verification Results

Check Status
tox -e format ✓ Pass
tox -e unit ✓ 2501 passed, 1 skipped
tox -e lint ✓ Pass
tox -e pre-push ✓ Pass (full CI suite)

API Usage Example

# Normal request
curl -X POST http://localhost:8000/api/matrix/bark \
  -H "Content-Type: application/json" \
  -d '{"text": "Hello Timmy!", "visitor_id": "visitor_123"}'

# Response
{
  "type": "bark",
  "agent_id": "timmy",
  "data": {
    "text": "Woof! Hello there!",
    "reply_to": null,
    "style": "speech"
  },
  "ts": 1742573952
}

Ready for review! 🚀

✅ **PR Created: #737** ## Implementation Complete ### Changes Made 1. **Added POST /api/matrix/bark endpoint** to `src/dashboard/routes/world.py` - Accepts JSON `{text: str, visitor_id: str}` - Returns bark message in `produce_bark()` format - Uses existing `_generate_bark()` for response generation - In-memory rate limiting: 1 request per 3 seconds per visitor_id - Returns 429 with `Retry-After` header when rate limited - Returns 422 for missing/invalid fields - Graceful fallback on LLM errors 2. **Added comprehensive tests** to `tests/dashboard/test_world_api.py` - 10 new test cases covering all functionality - Validates request requirements, rate limiting, response format, error handling ### Verification Results | Check | Status | |-------|--------| | `tox -e format` | ✓ Pass | | `tox -e unit` | ✓ 2501 passed, 1 skipped | | `tox -e lint` | ✓ Pass | | `tox -e pre-push` | ✓ Pass (full CI suite) | ### API Usage Example ```bash # Normal request curl -X POST http://localhost:8000/api/matrix/bark \ -H "Content-Type: application/json" \ -d '{"text": "Hello Timmy!", "visitor_id": "visitor_123"}' # Response { "type": "bark", "agent_id": "timmy", "data": { "text": "Woof! Hello there!", "reply_to": null, "style": "speech" }, "ts": 1742573952 } ``` Ready for review! 🚀
kimi closed this issue 2026-03-21 14:32:05 +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#675
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?