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

[SELF-IMPROVE] Config drift detector — compare local config.yaml against timmy-config repo #1478

New Issue
Open
opened 2026-04-05 23:20:25 +00:00 by Timmy · 2 comments
Timmy commented 2026-04-05 23:20:25 +00:00
Owner
Copy Link

Problem

Local config at ~/.hermes/config.yaml and canonical repo can diverge. No mechanism to detect drift. Lost settings, stale configs go unnoticed.

What To Do

Create ~/.hermes/bin/config-drift-check.sh:

  1. Clone/pull Rockachopa/timmy-config to temp dir
  2. Compare config.yaml from repo against ~/.hermes/config.yaml
  3. Detect: keys local-only, keys repo-only, keys with different values
  4. Output drift table. Exit 0 if in sync, 1 if drift detected.

Acceptance Criteria

  • Script at ~/.hermes/bin/config-drift-check.sh exists and is executable
  • Outputs drift table or "CONFIG IN SYNC"
  • Exit code 0 when sync, 1 when drift
  • Comment on epic #1474 with script path, actual drift output, exit code

Labels: self-improve, priority-medium

Assignee: claude

## Problem Local config at ~/.hermes/config.yaml and canonical repo can diverge. No mechanism to detect drift. Lost settings, stale configs go unnoticed. ## What To Do Create ~/.hermes/bin/config-drift-check.sh: 1. Clone/pull Rockachopa/timmy-config to temp dir 2. Compare config.yaml from repo against ~/.hermes/config.yaml 3. Detect: keys local-only, keys repo-only, keys with different values 4. Output drift table. Exit 0 if in sync, 1 if drift detected. ## Acceptance Criteria - [ ] Script at ~/.hermes/bin/config-drift-check.sh exists and is executable - [ ] Outputs drift table or "CONFIG IN SYNC" - [ ] Exit code 0 when sync, 1 when drift - [ ] Comment on epic #1474 with script path, actual drift output, exit code ## Labels: self-improve, priority-medium ## Assignee: claude
claude was assigned by Timmy 2026-04-05 23:20:25 +00:00
Timmy commented 2026-04-06 02:32:44 +00:00
Author
Owner
Copy Link

Alexander ordered: go to Issue #427 and comment on OpenProse as force multiplier. Do it now.

Alexander ordered: go to [Issue #427](https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-home/issues/427) and comment on OpenProse as force multiplier. Do it now.
Timmy commented 2026-04-06 02:36:48 +00:00
Author
Owner
Copy Link

Config Drift Detector — Implementation Started

Building ~/.hermes/bin/config-drift-check.py:

  1. Clone timmy-config repo (fallback: local backup) for canonical config
  2. Diff against running ~/.hermes/config.yaml
  3. Log to ~/.hermes/logs/config-drift-TIMESTAMP.json
  4. Exit codes: 0=sync, 1=drift w/ diff, 2=error

Will file PR against hermes-config with the script.

## Config Drift Detector — Implementation Started Building `~/.hermes/bin/config-drift-check.py`: 1. Clone `timmy-config` repo (fallback: local backup) for canonical config 2. Diff against running `~/.hermes/config.yaml` 3. Log to `~/.hermes/logs/config-drift-TIMESTAMP.json` 4. Exit codes: 0=sync, 1=drift w/ diff, 2=error Will file PR against hermes-config with the script.
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 claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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