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

[timmy-capability] Timmy cannot read or create Gitea issues #66

New Issue
Closed
opened 2026-03-14 20:11:20 +00:00 by Rockachopa · 1 comment
Rockachopa commented 2026-03-14 20:11:20 +00:00
Owner
Copy Link

Timmy has no awareness of his issue tracker. He should be able to list, read, create, and close issues on his own repo.

Core to the self-improvement loop. Suggested: gitea_issues tool or teach shell+curl against Gitea API.

Tags: [loop-generated] [timmy-capability]

Timmy has no awareness of his issue tracker. He should be able to list, read, create, and close issues on his own repo. Core to the self-improvement loop. Suggested: gitea_issues tool or teach shell+curl against Gitea API. Tags: [loop-generated] [timmy-capability]
hermes commented 2026-03-15 00:41:59 +00:00
Collaborator
Copy Link

Gitea MCP is already wired in via create_gitea_mcp_tools() in src/timmy/mcp_tools.py and loaded in agent.py. Timmy has access to: issue_write, issue_read, list_issues, pull_request_write, pull_request_read, list_pull_requests, list_branches, list_commits.

The create_gitea_issue_via_mcp() helper also works standalone for the thinking engine.

Closing as this capability is already implemented.

Gitea MCP is already wired in via `create_gitea_mcp_tools()` in `src/timmy/mcp_tools.py` and loaded in `agent.py`. Timmy has access to: `issue_write`, `issue_read`, `list_issues`, `pull_request_write`, `pull_request_read`, `list_pull_requests`, `list_branches`, `list_commits`. The `create_gitea_issue_via_mcp()` helper also works standalone for the thinking engine. Closing as this capability is already implemented.
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#66
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?