I built this toolkit using Claude Code on Claude Max. The entire project was developed with Claude Code as both the development tool and the target platform. The problem I kept hitting: during longer Claude Code sessions, execution logic (what to do next, managing multi-step tasks) and intelligence logic (reasoning and code generation) get tangled together. Sessions become harder to manage and debug. So I built a Python CLI toolkit that creates a clean separation: Execution layer (toolkit handles):
- Automated loop driver: keeps Claude Code running through multi-step workflows hands-off
- Custom slash commands: define reusable shortcuts for common operations
- Portfolio governance: manage multiple Claude Code projects from one interface Intelligence layer (Claude Code handles):
- Code generation and reasoning
- Architecture decisions
- Problem solving Bridge between layers:
- MCP browser bridge: connects CLI workflows to browser contexts via Model Context Protocol
- Council automation: orchestrates multi-model code review The loop driver has been the most useful feature for me personally - being able to define a complex multi-step task and let Claude Code work through it without manual intervention between steps. MIT licensed, pure Python: https://github.com/intellegix/intellegix-code-agent-toolkit Would love feedback from other Claude Code users. How are you managing longer autonomous sessions? submitted by /u/Agile_Detective4294
Originally posted by u/Agile_Detective4294 on r/ClaudeCode
You must log in or # to comment.