shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Feature - Agent Context Logging (Phase 3: Pattern Detection) #214

New Issue
Open
opened 2026-04-07 12:00:42 +02:00 by shoko · 0 comments
shoko commented 2026-04-07 12:00:42 +02:00
Owner
Copy Link

Summary

Phase 3 of Agent Context Logging - Aggregate context across issues to detect patterns for feedback-driven prompt improvements.

Background

Tracked by meta issue: #125 [META] Agent Context Logging

Phase 1 & 2 Scope (Completed separately)

  • Phase 1: Initial prompt capture
  • Phase 2: Session-end detection + final capture

Phase 3 Goal

Aggregate context across multiple issues to:

  • Detect recurring patterns (e.g., "dev agent forgets tests 5 times")
  • Enable human review of patterns
  • Inject learned improvements into future agent contexts

Research Required

Pattern Detection

  1. What patterns to detect?

    • Repeated mistakes
    • Missing steps (e.g., no tests added)
    • Communication issues

  2. How to detect?

    • Keyword matching?
    • ML/AI analysis?
    • Human-defined rules?

  3. What to do with patterns?

    • Flag for human review
    • Auto-generate prompt injections?
    • Store for analysis?

Context Aggregation

  1. Storage: Continue using ~/.kugetsu/context/ or create aggregated view?
  2. Retention: How long to keep aggregated data?
  3. Access: kugetsu contextlog analyze command?

Proposed Commands (from original #125)

kugetsu contextlog list              # List logged sessions
kugetsu contextlog show <session>   # Show context for session
kugetsu contextlog analyze          # Show pattern analysis
kugetsu contextlog prune <session>  # Delete log

Status

Blocked - 0.3.x milestone, depends on Phase 1 & 2.

## Summary Phase 3 of Agent Context Logging - Aggregate context across issues to detect patterns for feedback-driven prompt improvements. ## Background Tracked by meta issue: #125 [META] Agent Context Logging ## Phase 1 & 2 Scope (Completed separately) - Phase 1: Initial prompt capture - Phase 2: Session-end detection + final capture ## Phase 3 Goal Aggregate context across multiple issues to: - Detect recurring patterns (e.g., "dev agent forgets tests 5 times") - Enable human review of patterns - Inject learned improvements into future agent contexts ## Research Required ### Pattern Detection 1. **What patterns to detect?** - Repeated mistakes - Missing steps (e.g., no tests added) - Communication issues 2. **How to detect?** - Keyword matching? - ML/AI analysis? - Human-defined rules? 3. **What to do with patterns?** - Flag for human review - Auto-generate prompt injections? - Store for analysis? ### Context Aggregation 1. **Storage**: Continue using `~/.kugetsu/context/` or create aggregated view? 2. **Retention**: How long to keep aggregated data? 3. **Access**: `kugetsu contextlog analyze` command? ## Proposed Commands (from original #125) ``` kugetsu contextlog list # List logged sessions kugetsu contextlog show <session> # Show context for session kugetsu contextlog analyze # Show pattern analysis kugetsu contextlog prune <session> # Delete log ``` ## Status Blocked - 0.3.x milestone, depends on Phase 1 & 2.
shoko added the 0.3.x-only label 2026-04-07 12:00:42 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label 0.3.x-only
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#214
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?