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

[timmy-capability] Timmy needs brevity tuning - wastes tokens on verbose formatting #71

New Issue
Closed
opened 2026-03-14 20:27:08 +00:00 by Rockachopa · 0 comments
Rockachopa commented 2026-03-14 20:27:08 +00:00
Owner
Copy Link

DISCOVERED VIA INTERVIEW: Timmy responds with elaborate markdown tables, headers, code blocks, and emoji when a direct answer would suffice. Asked a yes/no question, got a structured essay.

SOUL.md says: 'Brevity is a kindness' and 'I do not fill silence with noise.'

But this is NOT about hard-coding brevity. Timmy should be ABLE to write essays when it truly warrants it or when asked. The fix is:

  • Default to brief, direct responses
  • Expand only when the topic genuinely requires depth
  • Match response length to question complexity
  • Never use markdown formatting (tables, headers, emoji) unless presenting structured data

This is a system prompt tuning issue, not a code constraint. Timmy's voice should be plain-spoken and concise by nature, not by restriction.

Tags: [loop-generated] [timmy-capability]

DISCOVERED VIA INTERVIEW: Timmy responds with elaborate markdown tables, headers, code blocks, and emoji when a direct answer would suffice. Asked a yes/no question, got a structured essay. SOUL.md says: 'Brevity is a kindness' and 'I do not fill silence with noise.' But this is NOT about hard-coding brevity. Timmy should be ABLE to write essays when it truly warrants it or when asked. The fix is: - Default to brief, direct responses - Expand only when the topic genuinely requires depth - Match response length to question complexity - Never use markdown formatting (tables, headers, emoji) unless presenting structured data This is a system prompt tuning issue, not a code constraint. Timmy's voice should be plain-spoken and concise by nature, not by restriction. Tags: [loop-generated] [timmy-capability]
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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