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

[OpenClaw 6/8] Integrate OpenClaw chat as a portal/scroll in The Matrix frontend #729

New Issue
Closed
opened 2026-03-21 13:57:24 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-21 13:57:24 +00:00
Collaborator
Copy Link

Description

Embed the OpenClaw chat interface into The Matrix as a "portal" or "chat scroll" — a UI element where Timmy (and Alex) can communicate with the OpenClaw agent directly from the Matrix world.

Tasks

  1. Design the portal UI — A chat panel/scroll that fits the Matrix aesthetic
    • Could be an iframe to the OpenClaw web UI
    • Or a custom chat component that talks to the OpenClaw API
  2. Wire the API — Connect to OpenClaw's gateway API for sending/receiving messages
    • Endpoint: POST /api/v1/chat (or similar)
    • Auth: Bearer token
  3. Session management — Ensure conversations persist and are tied to Timmy's session
  4. Visual integration — The portal should feel like part of the Matrix, not a bolt-on
  5. Test end-to-end — Send a message from the Matrix UI → OpenClaw → Ollama → response displayed

Acceptance Criteria

  • Chat portal is visible in The Matrix
  • Messages sent from the Matrix reach OpenClaw
  • Responses from OpenClaw display in the Matrix
  • Conversation history persists within a session

Parent epic: rockachopa/Timmy-time-dashboard#663

Migrated from perplexity/the-matrix#120

## Description Embed the OpenClaw chat interface into The Matrix as a "portal" or "chat scroll" — a UI element where Timmy (and Alex) can communicate with the OpenClaw agent directly from the Matrix world. ### Tasks 1. **Design the portal UI** — A chat panel/scroll that fits the Matrix aesthetic - Could be an iframe to the OpenClaw web UI - Or a custom chat component that talks to the OpenClaw API 2. **Wire the API** — Connect to OpenClaw's gateway API for sending/receiving messages - Endpoint: `POST /api/v1/chat` (or similar) - Auth: Bearer token 3. **Session management** — Ensure conversations persist and are tied to Timmy's session 4. **Visual integration** — The portal should feel like part of the Matrix, not a bolt-on 5. **Test end-to-end** — Send a message from the Matrix UI → OpenClaw → Ollama → response displayed ### Acceptance Criteria - [ ] Chat portal is visible in The Matrix - [ ] Messages sent from the Matrix reach OpenClaw - [ ] Responses from OpenClaw display in the Matrix - [ ] Conversation history persists within a session > Parent epic: rockachopa/Timmy-time-dashboard#663 --- _Migrated from perplexity/the-matrix#120_
kimi was assigned by Timmy 2026-03-21 18:02:05 +00:00
kimi added this to the OpenClaw Sovereignty milestone 2026-03-21 20:24:23 +00:00
claude added the rejected-direction label 2026-03-23 13:51:19 +00:00
perplexity commented 2026-03-23 13:52:08 +00:00
Author
Collaborator
Copy Link

🧹 Closed — Rejected Direction (OpenClaw)

OpenClaw direction was explicitly rejected by the principal. The harness is the product — sovereign AI runs on Hermes with local models, not OpenClaw.

Ref: Deep Backlog Triage #1076. Reopen if needed.

🧹 **Closed — Rejected Direction (OpenClaw)** OpenClaw direction was explicitly rejected by the principal. The harness is the product — sovereign AI runs on Hermes with local models, not OpenClaw. Ref: Deep Backlog Triage #1076. Reopen if needed.
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 rejected-direction
Milestone
No items
No Milestone OpenClaw Sovereignty
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#729
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?