24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
# 2026-03-04 Session Notes
|
|
|
|
## Extraction Timeout Configuration
|
|
|
|
Nicholai identified that users are experiencing Ollama timeouts after 45 seconds during memory extraction (45000ms). He requested that the timeout be increased by default and made configurable in the agent config settings.
|
|
|
|
The session focused on understanding the current timeout implementation in the daemon pipeline. An Explore agent was launched to trace where the 45000ms timeout is defined and used. Initial grep searches found the timeout referenced in 7 files:
|
|
- docs/PIPELINE.md
|
|
- docs/CONFIGURATION.md
|
|
- packages/daemon/src/memory-config.ts
|
|
- packages/daemon/src/repair-actions.test.ts
|
|
- packages/daemon/src/pipeline/provider.ts
|
|
- packages/daemon/src/pipeline/maintenance-worker.test.ts
|
|
- packages/cli/templates/agent.yaml.template
|
|
|
|
The agent began investigating the configuration surface (PipelineV2Config in packages/core/src/types.ts) and how defaults are set in packages/core/src/memory-config.ts to understand where the timeout configuration should be exposed.
|
|
|
|
## Next Steps
|
|
|
|
Implement configurable extraction timeout by:
|
|
1. Adding timeout field to PipelineV2Config in packages/core/src/types.ts
|
|
2. Setting reasonable default (longer than 45s) in packages/core/src/memory-config.ts
|
|
3. Exposing the setting in agent.yaml config template
|
|
4. Updating packages/daemon/src/pipeline/provider.ts to use configurable timeout instead of hardcoded 45000ms |