too many terminals, not enough tentacles

![Last Update](https://img.shields.io/github/last-commit/hesamsheikh/octogent?label=Last%20Update&style=flat-square) [![TypeScript](https://img.shields.io/badge/TypeScript-5.8-3178C6?style=flat-square&logo=typescript&logoColor=white)](https://www.typescriptlang.org/) [![Node.js](https://img.shields.io/badge/Node.js-22+-5FA04E?style=flat-square&logo=node.js&logoColor=white)](https://nodejs.org/) [![Follow on X](https://img.shields.io/badge/Follow%20on-X-000000?style=flat-square&logo=x)](https://x.com/Hesamation) [![Discord](https://img.shields.io/badge/Discord-Open%20Source%20AI%20Builders-5865F2?style=flat-square&logo=discord&logoColor=white)](https://discord.gg/vtJykN3t)

# 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 agent-readable markdown such as `CONTEXT.md`, `todo.md`, and any extra notes needed for that slice of the codebase. The octopus metaphor is literal: *one octopus, many tentacles, different work happening at the same time*. ## Tentacles A **tentacle** is a scoped job container. It gives one slice of work its own files, notes, and `todo.md` so the agent is not forced to reconstruct the entire codebase context from chat history. What it does: - keeps context local to one area such as documentation, database work, API changes, or frontend work - gives agents durable files they can read and update - provides a natural source for delegation through todo items For the full model, s