forked from Rockachopa/Timmy-time-dashboard
5b6d33e05a
* feat: add task queue system for Timmy - all work goes through the queue - Add queue position tracking to task_queue models with task_type field - Add TaskProcessor class that consumes tasks from queue one at a time - Modify chat route to queue all messages for async processing - Chat responses get 'high' priority to jump ahead of thought tasks - Add queue status API endpoints for position polling - Update UI to show queue position (x/y) and current task banner - Replace thinking loop with task-based approach - thoughts are queued tasks - Push responses to user via WebSocket instead of immediate HTTP response - Add database migrations for existing tables * feat: Timmy drains task queue on startup, backlogs unhandleable tasks On spin-up, Timmy now iterates through all pending/approved tasks immediately instead of waiting for the polling loop. Tasks without a registered handler or with permanent errors are moved to a new BACKLOGGED status with a reason, keeping the queue clear for work Timmy can actually do. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Alexander Payne <apayne@MM.local> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
44 lines
816 B
Markdown
44 lines
816 B
Markdown
# User Profile
|
|
|
|
> Learned information about the user. Updated continuously.
|
|
|
|
## Basic Information
|
|
|
|
**Name:** Not
|
|
**Location:** (unknown)
|
|
**Occupation:** (unknown)
|
|
**Technical Level:** (to be assessed)
|
|
|
|
## Interests & Expertise
|
|
|
|
- (to be learned from conversations)
|
|
|
|
## Preferences
|
|
|
|
### Communication
|
|
- Response style: (default: concise, technical)
|
|
- Detail level: (default: medium)
|
|
- Humor: (default: minimal)
|
|
|
|
### Tools
|
|
- Auto-tool usage: (default: minimal)
|
|
- Confirmation required for: shell commands, file writes
|
|
|
|
### Memory
|
|
- Personalization: Enabled
|
|
- Context retention: 20 messages (working), 100 (short-term)
|
|
|
|
## Important Facts
|
|
|
|
- (to be extracted from conversations)
|
|
|
|
## Relationship History
|
|
|
|
- First session: 2026-02-25
|
|
- Total sessions: 1
|
|
- Key milestones: (none yet)
|
|
|
|
---
|
|
|
|
*Last updated: 2026-02-27*
|