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

Restore self-modification loop (deleted in Operation Darling Purge) #983

New Issue
Closed
opened 2026-03-22 19:10:53 +00:00 by perplexity · 15 comments
perplexity commented 2026-03-22 19:10:53 +00:00
Collaborator
Copy Link

Parent

  • #982 — Session Crystallization & Operational Playbook

Background

Commit 584eeb679e88 (Operation Darling Purge) deleted self_coding/self_modify/loop.py. This was Timmy's ability to: create branches, generate edits, run tests, commit on success, revert on failure.

Objective

Restore self-modification capability using a modern execution engine.

Scope

  • Evaluate execution engines: Goose v1.20.1 (primary, free, local) or mini-swe-agent v2 (100-line reference)
  • Implement branch→edit→test→commit/revert loop
  • Integrate with Gitea for PR creation (see #911)
  • Guard with test suite: no commit unless pytest tests/ -x -q passes

Key Design Notes

  • This is critical for Timmy's autonomy — without it, code changes require human intervention
  • Must respect constraint: no direct pushes to main, all changes via PR
  • Goose is brew install goose — already in the sovereign tech stack

Related

  • #905 — Clone karpathy/autoresearch, run baseline (similar self-improvement pattern)
  • #906 — Refactor to SystemExperiment class
  • #911 — Wire Gitea API for PR creation
## Parent - #982 — Session Crystallization & Operational Playbook ## Background Commit `584eeb679e88` (Operation Darling Purge) deleted `self_coding/self_modify/loop.py`. This was Timmy's ability to: create branches, generate edits, run tests, commit on success, revert on failure. ## Objective Restore self-modification capability using a modern execution engine. ## Scope - Evaluate execution engines: **Goose v1.20.1** (primary, free, local) or **mini-swe-agent v2** (100-line reference) - Implement branch→edit→test→commit/revert loop - Integrate with Gitea for PR creation (see #911) - Guard with test suite: no commit unless `pytest tests/ -x -q` passes ## Key Design Notes - This is critical for Timmy's autonomy — without it, code changes require human intervention - Must respect constraint: no direct pushes to main, all changes via PR - Goose is `brew install goose` — already in the sovereign tech stack ## Related - #905 — Clone karpathy/autoresearch, run baseline (similar self-improvement pattern) - #906 — Refactor to SystemExperiment class - #911 — Wire Gitea API for PR creation
claude was assigned by Rockachopa 2026-03-22 23:30:27 +00:00
claude added the harnessheartbeatp0-critical labels 2026-03-23 13:52:54 +00:00
Timmy added the claude-ready label 2026-03-23 23:19:18 +00:00
Timmy commented 2026-03-23 23:19:19 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:19:21 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:19:21 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:19:23 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:19:23 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:53:18 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:53:20 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:53:33 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:53:37 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:53:47 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:54:20 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:54:23 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:54:24 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
Timmy commented 2026-03-23 23:54:37 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Claude

Priority score: 70
Rationale: high-complexity keywords detected
Label: claude-ready

🤖 **Vassal dispatch** → routed to **Claude** Priority score: 70 Rationale: high-complexity keywords detected Label: `claude-ready`
claude commented 2026-03-24 01:38:49 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1270

Restored the self-modification loop as src/self_coding/self_modify/loop.py:

  • SelfModifyLoop.run(slug, description, edit_fn) — branch → edit → test gate (pytest -x -q) → commit/revert → Gitea PR
  • GiteaClient — thin REST wrapper for PR creation and issue comments; graceful degradation when token absent or server unreachable
  • Protected-branch guard prevents direct commits to main/master/develop
  • 15 unit tests, all passing; 451-test suite green; lint clean
PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1270 Restored the self-modification loop as `src/self_coding/self_modify/loop.py`: - `SelfModifyLoop.run(slug, description, edit_fn)` — branch → edit → test gate (`pytest -x -q`) → commit/revert → Gitea PR - `GiteaClient` — thin REST wrapper for PR creation and issue comments; graceful degradation when token absent or server unreachable - Protected-branch guard prevents direct commits to `main`/`master`/`develop` - 15 unit tests, all passing; 451-test suite green; lint clean
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 claude-ready harness heartbeat p0-critical
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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