30 lines
1006 B
Markdown
30 lines
1006 B
Markdown
# Design Rationale
|
|
|
|
## Core Structure
|
|
The procedure is designed to maintain a clean conversation flow while ensuring all necessary information is available.
|
|
The flow focuses on:
|
|
|
|
1. **Context management**
|
|
- Load basic user info immediately to ensure proper interaction
|
|
- Recent conversation history provides continuity
|
|
- Clean context when usage exceeds 50%
|
|
- Gather only what's needed for the current conversation
|
|
- Skip gathering if it would slow down the interaction
|
|
|
|
2. **Message Management**
|
|
- Draft-review-revise cycle for quality
|
|
- Automatic history tracking for both user and agent messages
|
|
- Clear file naming convention using entry IDs
|
|
|
|
3. **Script Handling**
|
|
- Pre-execution estimation of runtime and output
|
|
- Explicit acceptability check before running
|
|
- Timeout and output limits for safety
|
|
|
|
4. **Response Timing**
|
|
- Adaptive busy wait with exponential backoff
|
|
- Clear decision point for wait vs end
|
|
- Proper context cleanup on exit
|
|
|
|
## Usage History
|