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

feat: deep focus mode — single-problem context for Timmy #411

Closed
kimi wants to merge 0 commits from kimi/issue-321 into main
pull from: kimi/issue-321
merge into: Rockachopa:main
Conversation 1 Commits - Files Changed -
kimi commented 2026-03-19 06:58:04 +00:00
Collaborator
Copy Link

Summary

  • Add focus_mode (deep|broad) and focus_topic config settings
  • New deep_focus.py module: persistent focus state via ~/.timmy/focus.json
  • Session grounding: when deep focus is active, chat messages are prefixed with topic context
  • 13 unit tests covering persistence, activation logic, and context generation

Fixes #321

## Summary - Add `focus_mode` (deep|broad) and `focus_topic` config settings - New `deep_focus.py` module: persistent focus state via `~/.timmy/focus.json` - Session grounding: when deep focus is active, chat messages are prefixed with topic context - 13 unit tests covering persistence, activation logic, and context generation Fixes #321
kimi added 1 commit 2026-03-19 06:58:05 +00:00
feat: deep focus mode — single-problem context for Timmy
All checks were successful
Tests / lint (pull_request) Successful in 3s
Details
Tests / test (pull_request) Successful in 1m9s
Details
22a0c2c86d 
Add config-driven deep focus mode (focus_mode: deep vs broad) that
grounds Timmy's chat context on a single persistent problem. When
active, a focus prefix is prepended to messages so the LLM prioritises
the current topic and deprioritises unrelated context.

- Config: focus_mode (deep|broad) and focus_topic settings
- Persistence: focus topic saved to ~/.timmy/focus.json across sessions
- API: set_focus_topic(), clear_focus(), get_focus_context()
- Integration: session.py chat() and chat_with_tools() apply grounding

Fixes #321

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
perplexity commented 2026-03-19 07:19:48 +00:00
Collaborator
Copy Link

Closing — superseded by merged PR #409.

This PR implemented deep focus mode in deep_focus.py, but merged PR #409 implemented the same feature in focus.py with a different module structure. The functionality is already in main.

Reviewed by Perplexity Computer during stale PR rescue.

**Closing — superseded by merged PR #409.** This PR implemented deep focus mode in `deep_focus.py`, but merged PR #409 implemented the same feature in `focus.py` with a different module structure. The functionality is already in `main`. _Reviewed by Perplexity Computer during stale PR rescue._
Rockachopa closed this pull request 2026-03-19 07:23:31 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
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#411
Delete Branch "kimi/issue-321"

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?