[ROUTING] Streamline local Timmy automation context per job (narrow toolsets, avoid prompt bloat) #90

New Issue

Timmy · 2026-03-29T12:38:23Z

Timmy commented

2026-03-29 12:38:23 +00:00

Goal:
Make local Timmy automation use job-specific, aggressively narrowed context so local llama.cpp lanes do not choke on oversized tool/system prompts.

Problem observed:

local Hermes4 sessions can loop or thrash when too many tools + large prompt/schema baggage are loaded
in the Alexander tmux Morrowind lane, narrowing the tool surface fixed the context-overflow behavior and restored a real response

Decision / marked solution:

the solution is NOT to keep inflating context windows
the solution is to load only the toolset(s) required for the current job
for gameplay/runtime lanes, prefer single-purpose toolset loads over the broad default tool inventory

Acceptance criteria:

define the canonical pattern for launching narrow local job lanes (for example Morrowind/gameplay lanes)
ensure future Timmy automation paths choose toolsets per job instead of inheriting broad defaults
document when to omit extra skills entirely if the toolset alone is sufficient
include proof that the narrowed lane avoids the previous loop/context overflow failure
preserve world-state evidence and operator visibility

Guardrail:

this is about context discipline, not builder work
keep the fix in the harness/config/launcher layer, not by growing bespoke runtime code

Goal: Make local Timmy automation use job-specific, aggressively narrowed context so local llama.cpp lanes do not choke on oversized tool/system prompts. Problem observed: - local Hermes4 sessions can loop or thrash when too many tools + large prompt/schema baggage are loaded - in the Alexander tmux Morrowind lane, narrowing the tool surface fixed the context-overflow behavior and restored a real response Decision / marked solution: - the solution is NOT to keep inflating context windows - the solution is to load only the toolset(s) required for the current job - for gameplay/runtime lanes, prefer single-purpose toolset loads over the broad default tool inventory Acceptance criteria: - define the canonical pattern for launching narrow local job lanes (for example Morrowind/gameplay lanes) - ensure future Timmy automation paths choose toolsets per job instead of inheriting broad defaults - document when to omit extra skills entirely if the toolset alone is sufficient - include proof that the narrowed lane avoids the previous loop/context overflow failure - preserve world-state evidence and operator visibility Guardrail: - this is about context discipline, not builder work - keep the fix in the harness/config/launcher layer, not by growing bespoke runtime code

Timmy self-assigned this 2026-03-29 12:38:23 +00:00

Timmy commented

2026-03-29 12:39:07 +00:00

Marked as the solution direction: narrow toolsets/context per job for local lanes instead of trying to brute-force larger contexts. This issue is the durable tracking front.

Timmy referenced this issue from Timmy_Foundation/the-nexus

2026-03-29 12:39:08 +00:00

[PORTAL] Deterministic Morrowind pilot loop with world-state proof #673

Timmy commented

2026-03-30 15:58:18 +00:00

Uniwizard context: Prompt routing is now #88 in timmy-home. This issue's narrow-toolset concept feeds into adaptive prompt routing tiers (reflex/standard/deep).

Timmy commented

2026-03-30 16:49:50 +00:00

Absorbed into timmy-home #88 (adaptive prompt routing). Closing duplicate.

Timmy closed this issue

2026-03-30 16:49:51 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#90