Octogent

too many terminals, not enough tentacles

Octogent

It's really not fun to have ten Claude Code sessions open at once, constantly switching between them and trying to remember what each one was supposed to do. *Things get blurry fast* when one agent is doing documentation, another is touching the database, another is changing the API, and another is somewhere in the frontend. Octogent tries to fix that by giving each job its own scoped context, notes, and task list, while also making it possible for Claude Code to spawn other Claude Code agents, assign them work, and communicate with them.

The Vision

This repo is a personal exploration of what an AI coding environment might look like when terminal coding agents are treated as parts of a bigger orchestration layer, not the final interface by themselves. The point is not to hide Claude Code behind abstractions. The point is to make *multi-agent work less chaotic for the developer* on a real codebase.

Screenshots

What Octogent Does for You

- Creates tentacles as context layers so agents can work with scoped markdown files instead of broad, messy chat context
- Uses todo.md as an execution surface so tasks stay visible, trackable, and ready for delegation
- Runs multiple Claude Code terminals so one developer can coordinate several coding sessions at once
- Spawns child agents from todo items so parallel work has a concrete source of truth
- Supports inter-agent messaging so workers and coordinators can report completion, blockers, and handoff notes
- Keeps agent-facing context in files so the system is more durable than a single prompt thread
- Provides a local API and UI for terminal lifecycle, persistence, websocket transport, and orchestration

A tentacle is a folder under .octogent/tentacles// that holds…