UniqueSoft/APAW
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

[Evolution] Context Window — Gitea-Centric Checkpoint Pruning + Agent Context Hygiene #114

New Issue
Closed
opened 2026-05-18 14:55:47 +00:00 by NW · 0 comments
NW commented 2026-05-18 14:55:47 +00:00
Owner
Copy Link

Evolution Summary

Type: Context Window Hardening
Date: 2026-05-18T15:50:00+01:00

Problem

Agents loaded full issue comment history (200+ comments = 15,000+ tokens), build logs, unrelated rules — pushing context to 80–90% before work began.

Solution

  • Gitea as single source of truth: All old state lives in Gitea comments, not agent RAM
  • Checkpoint pruning: If consumed > 80%, truncate history to last 3 entries, archive rest to comment
  • Agent context hygiene: Load ONLY checkpoint + last 3 comments + ≤3 files + 1 skill + 1 rule

New Files

  • .kilo/rules/context-window-budget.md — budget tables, what NOT to load, recovery protocol
  • .kilo/rules/gns-checkpoint-pruning.md — minimal checkpoint v2, entry/exit protocols, pagination

Updated Files

  • .kilo/agents/orchestrator.md — Context Budget Governance section
  • .kilo/rules/gns-agent-protocol.md — checkpoint schema trimmed, added current_task + agent_chain
  • .kilo/EVOLUTION_LOG.md — evolution entry #5

Commit

46d6752 — feat(context-window): evolution — Gitea-centric checkpoint pruning + agent context hygiene

Expected Impact

  • Context token reduction: ~12,000 per invocation
  • Context window availability: 10% → 60% (6x more room for reasoning)

/close

## Evolution Summary Type: **Context Window Hardening** Date: 2026-05-18T15:50:00+01:00 ### Problem Agents loaded full issue comment history (200+ comments = 15,000+ tokens), build logs, unrelated rules — pushing context to 80–90% before work began. ### Solution - **Gitea as single source of truth**: All old state lives in Gitea comments, not agent RAM - **Checkpoint pruning**: If `consumed > 80%`, truncate history to last 3 entries, archive rest to comment - **Agent context hygiene**: Load ONLY checkpoint + last 3 comments + ≤3 files + 1 skill + 1 rule ### New Files - `.kilo/rules/context-window-budget.md` — budget tables, what NOT to load, recovery protocol - `.kilo/rules/gns-checkpoint-pruning.md` — minimal checkpoint v2, entry/exit protocols, pagination ### Updated Files - `.kilo/agents/orchestrator.md` — Context Budget Governance section - `.kilo/rules/gns-agent-protocol.md` — checkpoint schema trimmed, added current_task + agent_chain - `.kilo/EVOLUTION_LOG.md` — evolution entry #5 ### Commit `46d6752` — `feat(context-window): evolution — Gitea-centric checkpoint pruning + agent context hygiene` ### Expected Impact - Context token reduction: ~12,000 per invocation - Context window availability: 10% → 60% (6x more room for reasoning) /close
NW closed this issue 2026-05-18 14:56:20 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agent::agent-architect
Owned by agent-architect
 agent::capability-analyst
Owned by capability-analyst
 agent::code-skeptic
Owned by code-skeptic
 agent::evaluator
Owned by evaluator
 agent::history-miner
Owned by history-miner
 agent::lead-developer
Owned by lead-developer
 agent::orchestrator
Owned by orchestrator
 agent::sdet-engineer
Owned by sdet-engineer
 agent::system-analyst
Owned by system-analyst
 agent::the-fixer
Owned by the-fixer
 budget::exhausted
Token budget exhausted
 budget::sufficient
Token budget sufficient
 budget::warning
Token budget low
 cascade::depth-0
No subagent calls
 cascade::depth-1
1-level subagent calls
 cascade::depth-2
2-level subagent calls
 cascade::depth-exceeded
Depth limit exceeded
 cascade::depth-n
Unlimited subagent calls
 dashboard::frozen
Dashboard feature freeze — no new features until thaw
 evolution::model-change
Model change evolution
 evolution::new-agent
New agent evolution
 evolution::new-skill
New skill evolution
 evolution::new-workflow
New workflow evolution
 evolution::prompt-opt
Prompt optimization evolution
 memory::checkpoint
Checkpoint stored
 memory::fresh
Checkpoint fresh
 memory::recoverable
Checkpoint recoverable
 memory::stale
Checkpoint stale
 permission::evolve-system
Can evolve system
 permission::read-only
Read-only access
 permission::violation
Security violation
 permission::write-code
Can write code
 permission::write-config
Can write config
 phase::awaiting-review
Agent awaits review
 phase::drafting-spec
Agent is drafting specification
 phase::executing
Agent is executing task
 phase::gathering-evidence
Agent is gathering data
 phase::refining-prompt
Agent is refining prompts
 phase::researching
Research phase — gathering evidence and solutions
 phase::verifying
Agent is verifying results
 priority::critical
Critical priority
 priority::high
High priority
 priority::low
Low priority
 priority::medium
Medium priority
 quality::blocked
Blocked by quality
 quality::fail
Quality check failed
 quality::needs-fix
Needs fixes
 quality::pass
Quality check passed
 size::l
Large (4-8 hours)
 size::m
Medium (2-4 hours)
 size::s
Small (1-2 hours)
 size::xl
Extra large (>8 hours)
 size::xs
Extra small (<1 hour)
 status::blocked
Blocked
 status::cancelled
Cancelled
 status::done
Completed
 status::in-progress
Work in progress
 status::new
New issue, not started
 status::planned
Planned for sprint
 status::review
Under review
 status::testing
In testing
 type::bug
Something is broken
 type::chore
Maintenance task
 type::documentation
Documentation
 type::enhancement
Improvement
 type::feature
New feature
 type::refactor
Code refactoring
 type::test
Testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
NW olilovedani
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: UniqueSoft/APAW#114
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?