dev/disclaw
1
0
Fork 0
Code Issues 9 Pull requests 1 Projects Releases Packages Wiki Activity Actions

KI-003: Hoher Token-Verbrauch durch vollständige History-Injection #36

New issue
Open
opened 2026-04-09 14:57:03 +00:00 by dev · 0 comments
dev commented 2026-04-09 14:57:03 +00:00
Owner
Copy link

Problem: Bei jeder Nachricht wird der gesamte Konversations-Verlauf als Text in den Prompt injiziert. Bei längeren Chats steigen Token-Kosten und Latenz stark an.

Mögliche Lösungen

  • --resume <session-id> (Claude Code, Phase 2) statt manueller History-Injection
  • max_history_messages in disclaw.yaml (konfigurierbares Limit)
  • Summary-Compression älterer History
  • Token-Counter per Conversation in DB

Details: docs/ideas/known-issues.md → KI-003

**Problem**: Bei jeder Nachricht wird der gesamte Konversations-Verlauf als Text in den Prompt injiziert. Bei längeren Chats steigen Token-Kosten und Latenz stark an. **Mögliche Lösungen** - `--resume <session-id>` (Claude Code, Phase 2) statt manueller History-Injection - `max_history_messages` in `disclaw.yaml` (konfigurierbares Limit) - Summary-Compression älterer History - Token-Counter per Conversation in DB Details: `docs/ideas/known-issues.md` → KI-003
dev added the
type:known-issue
 label 2026-04-09 14:57:03 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
refinement/mapped-project-paths
No results found.
Labels
Clear labels   
blocked

Blockiert durch andere Issue

  
needs-review

Wartet auf Review

  
phase:0

Phase 0 � H�rtung

  
phase:1

Phase 1 � Solides MVP

  
phase:1.5

   
phase:2

Phase 2 � Context-Effizienz

  
phase:3

Phase 3 � UX

  
phase:4

Phase 4 � Skills & Permissions

  
phase:5

Phase 5 � Streaming

  
phase:6+

Phase 6+ � Zukunft

  
priority:p0

Kritisch � sofort

  
priority:p1

Hoch

  
priority:p2

Normal

  
security

Sicherheitsrelevant

  
type:chore

Chore / Build

  
type:ci

CI/CD Pipeline

  
type:docs

Dokumentation

  
type:feat

Neues Feature

  
type:fix

Bugfix

  
type:idea

   
type:known-issue

   
type:refactor

Refactoring

  
type:test

Tests

No labels
blocked
needs-review
phase:0
phase:1
phase:1.5
phase:2
phase:3
phase:4
phase:5
phase:6+
priority:p0
priority:p1
priority:p2
security
type:chore
type:ci
type:docs
type:feat
type:fix
type:idea
type:known-issue
type:refactor
type:test
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: dev/disclaw#36
No description provided.
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?