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

Implement Timmy control panel CLI entry point #702

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

Description

Add a single entry point (e.g., timmyctl or similar) that acts as Timmy's primary control surface for automations. It should expose subcommands such as:

  • timmyctl daily-run – run the Daily Run orchestration (agenda + summary)
  • timmyctl log-run – capture a quick Daily Run logbook entry
  • timmyctl inbox – show what's "calling Timmy" (PRs, Daily Run items, alerts)
  • timmyctl config – display key config (labels, logbook issue ID, token rules overview)

The control panel should be easy to extend with future subcommands and should read configuration from files under timmy_automations/config/.

Acceptance Criteria

  • Running the command locally shows the listed subcommands with help text
  • Everyday interactions with automations can be done through this single entry point
  • Configuration is file-driven and does not require code changes for common tweaks

From: Timmy Automations Backlog §1.2

Migrated from perplexity/the-matrix#93

## Description Add a single entry point (e.g., `timmyctl` or similar) that acts as Timmy's primary control surface for automations. It should expose subcommands such as: - `timmyctl daily-run` – run the Daily Run orchestration (agenda + summary) - `timmyctl log-run` – capture a quick Daily Run logbook entry - `timmyctl inbox` – show what's "calling Timmy" (PRs, Daily Run items, alerts) - `timmyctl config` – display key config (labels, logbook issue ID, token rules overview) The control panel should be easy to extend with future subcommands and should read configuration from files under `timmy_automations/config/`. ## Acceptance Criteria - [ ] Running the command locally shows the listed subcommands with help text - [ ] Everyday interactions with automations can be done through this single entry point - [ ] Configuration is file-driven and does not require code changes for common tweaks _From: Timmy Automations Backlog §1.2_ --- _Migrated from perplexity/the-matrix#93_
kimi was assigned by Timmy 2026-03-21 18:02:17 +00:00
kimi commented 2026-03-21 19:15:14 +00:00
Collaborator
Copy Link

PR Created: #767

Implemented timmyctl CLI entry point for Timmy automations control panel.

Commands Implemented

Command Purpose
timmyctl daily-run Run Daily Run orchestration with schedules & triggers display
timmyctl log-run <msg> Capture timestamped logbook entries
timmyctl inbox Show active automations, PRs, and issues calling for attention
timmyctl config [key] Display automations config, triage rules

Acceptance Criteria

  • ✅ Running the command locally shows the listed subcommands with help text
  • ✅ Everyday interactions with automations can be done through this single entry point
  • ✅ Configuration is file-driven (reads from timmy_automations/config/ — JSON/YAML)

Quality Checks

  • All 2650+ unit tests pass
  • Lint and formatting clean
  • Follows existing Typer CLI patterns from timmy and timmy-serve

The CLI is extensible — new subcommands can be added following the existing pattern in src/timmyctl/cli.py.

## PR Created: #767 Implemented `timmyctl` CLI entry point for Timmy automations control panel. ### Commands Implemented | Command | Purpose | |---------|---------| | `timmyctl daily-run` | Run Daily Run orchestration with schedules & triggers display | | `timmyctl log-run <msg>` | Capture timestamped logbook entries | | `timmyctl inbox` | Show active automations, PRs, and issues calling for attention | | `timmyctl config [key]` | Display automations config, triage rules | ### Acceptance Criteria - ✅ Running the command locally shows the listed subcommands with help text - ✅ Everyday interactions with automations can be done through this single entry point - ✅ Configuration is file-driven (reads from `timmy_automations/config/` — JSON/YAML) ### Quality Checks - All 2650+ unit tests pass - Lint and formatting clean - Follows existing Typer CLI patterns from `timmy` and `timmy-serve` The CLI is extensible — new subcommands can be added following the existing pattern in `src/timmyctl/cli.py`.
kimi closed this issue 2026-03-21 19:15:28 +00:00
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 kimi
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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