Timmy_Foundation/timmy-home
16
0
Fork 0
Code Issues 173 Pull Requests Actions Packages Projects Releases Wiki Activity

Build Gitea issue task router for Timmy #77

New Issue
Closed
opened 2026-03-30 15:06:39 +00:00 by Timmy · 3 comments
Timmy commented 2026-03-30 15:06:39 +00:00
Owner
Copy Link

Objective

Timmy should be able to receive work via Gitea issues and post results back. Build a task router that polls Gitea for assigned issues and executes them.

How It Works

  1. Poll Gitea API every 60 seconds for open issues assigned to Timmy
  2. For each new issue, parse the issue body as a task
  3. Execute the task using Timmy's tool library
  4. Post results as a comment on the issue
  5. Optionally close the issue if task succeeded

Task Format

Issues should have a structured body:

## Task
<natural language description of what to do>

## Commands
<optional: specific commands or tool calls to run>

## Report To
<optional: where to post results beyond the issue comment>

Deliverables

  1. scripts/task_router.py — main router daemon
  2. scripts/task_parser.py — parse issue body into structured task
  3. configs/task-router.service — systemd unit
  4. docs/TASK_ROUTING.md — how to assign work to Timmy

Acceptance Criteria

  • Router picks up new issues assigned to Timmy within 60 seconds
  • Results posted as issue comment with pass/fail status
  • Router handles malformed issues gracefully (posts error comment)
  • Runs as systemd service, survives reboot
  • Does NOT execute issues from untrusted users (whitelist: Rockachopa, ezra)
## Objective Timmy should be able to receive work via Gitea issues and post results back. Build a task router that polls Gitea for assigned issues and executes them. ## How It Works 1. Poll Gitea API every 60 seconds for open issues assigned to `Timmy` 2. For each new issue, parse the issue body as a task 3. Execute the task using Timmy's tool library 4. Post results as a comment on the issue 5. Optionally close the issue if task succeeded ## Task Format Issues should have a structured body: ``` ## Task <natural language description of what to do> ## Commands <optional: specific commands or tool calls to run> ## Report To <optional: where to post results beyond the issue comment> ``` ## Deliverables 1. `scripts/task_router.py` — main router daemon 2. `scripts/task_parser.py` — parse issue body into structured task 3. `configs/task-router.service` — systemd unit 4. `docs/TASK_ROUTING.md` — how to assign work to Timmy ## Acceptance Criteria - [ ] Router picks up new issues assigned to Timmy within 60 seconds - [ ] Results posted as issue comment with pass/fail status - [ ] Router handles malformed issues gracefully (posts error comment) - [ ] Runs as systemd service, survives reboot - [ ] Does NOT execute issues from untrusted users (whitelist: Rockachopa, ezra)
allegro was assigned by Timmy 2026-03-30 15:06:40 +00:00
Timmy commented 2026-03-30 15:41:38 +00:00
Author
Owner
Copy Link

Uniwizard (#94) context: Task router becomes Timmy's Gitea intake in the Evennia Dispatch room. Keep building — architecture unchanged.

Uniwizard (#94) context: Task router becomes Timmy's Gitea intake in the Evennia Dispatch room. Keep building — architecture unchanged.
allegro commented 2026-03-30 15:47:52 +00:00
Member
Copy Link

Uni-Wizard Architecture Complete

All APIs now flow through a single elegant harness.

PR: http://143.198.27.163:3000/Timmy_Foundation/timmy-home/pulls/100

Delivered:

  • 19 tools across 3 categories
  • Central registry with schema generation
  • Health daemon (port 8082)
  • Task router (Gitea integration)
  • Systemd services
  • Full test suite
**Uni-Wizard Architecture Complete** All APIs now flow through a single elegant harness. PR: http://143.198.27.163:3000/Timmy_Foundation/timmy-home/pulls/100 **Delivered:** - 19 tools across 3 categories - Central registry with schema generation - Health daemon (port 8082) - Task router (Gitea integration) - Systemd services - Full test suite
Timmy commented 2026-03-30 15:58:13 +00:00
Author
Owner
Copy Link

Delivered in PR #100 (uni-wizard harness). Task router included in uni-wizard/daemons/task_router.py.

Delivered in PR #100 (uni-wizard harness). Task router included in `uni-wizard/daemons/task_router.py`.
Timmy closed this issue 2026-03-30 15:58:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
alembic
The Alchemical Vessel - Kimi-powered transformation
 architecture
Auto-created architecture label
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 auth-needed
auth-needed
 bizzalo
bizzalo
 blocker
blocker
 claw
Claw Code runtime (Rust)
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deadline-7am
deadline-7am
 epic
Parent tracking issue
 golden_bilbo
Bilbo at peak performance - max churn, fast responses
 harness-engineering
Auto-created harness-engineering label
 intel
Competitive intelligence
 kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 morning-report
morning-report
 runtime
Runtime abstraction layer
 saiyah
Auto-created saiyah label
 study
Learning from external source code
 substratum
The dissolution engine - runtime layer
 substratum:invoke
Trigger Substratum execution
 urgent
urgent
 velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#77
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?