Software Orchestrator
5769c1cd22
- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung) - 25 Tests gruen (Pytest) - block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block) - 4 Restbaustellen gefixt - DB-Schema: plugin_settings-Tabelle hinzugefuegt - 3 Schattenprojekte aus DB geloescht - Plan v3 + Refactor-Plan + Worklog dokumentiert
1.2 KiB
1.2 KiB
name, description, tags
| name | description | tags | |||
|---|---|---|---|---|---|
| error-tracking | Known errors lifecycle management and recovery for the orchestrator agent. |
|
Error Tracking
Purpose
Track known errors across sessions, document their root cause and solution, and reuse the knowledge for future occurrences.
When to Use
- When a tool or subordinate returns a persistent error
- When a code block fails compilation or tests
- When the agent encounters an unknown error
- After resolution to log the solution
When Not to Use
- For transient network blips (retry once, then log)
- For user input errors (request clarification instead)
Procedure: Error Logging
- Capture full error output (stack trace, message, context)
- Search the library for similar past errors (use library-query)
- If a similar error exists, apply the documented solution
- If new error, document: title, symptom, cause, fix, tags, project_id
- Extract to library (use library-extractor) for future reference
Procedure: Resolution
- Apply minimal targeted fix
- Run tests to verify
- Commit the fix
- Update error entry with resolution status
See Also
- Help:
library/extract.md - Help:
library/query.md - Tool:
error_handler(if available in plugin)