Create spaces, add multiple Claude agents to your project folders, and chat with them together — like a group messenger. 🐙
Features
💬 Natural Chat Interface
Talk to your AI agents through an intuitive chat UI. Markdown rendering, real-time streaming, and a familiar messaging experience.
🐙 .octo Agents
Define agents as simple .octo files. Each file is an independent agent with its own role, personality, and capabilities. Delete the file, delete the agent. Copy it, clone the agent.
🧠 Hidden Orchestrator
A smart orchestrator reads the context and calls the right agent at the right time. You direct, agents collaborate.
🔗 Agent-to-Agent
Agents @mention each other and trigger chain reactions. A developer agent asks the designer for feedback, a planner coordinates tasks — all without your intervention.
📁 Spaces & Folders
Create multiple spaces and add folders to each. Organize different agent teams for different projects, all in one app.
📝 Shared Wiki
A shared knowledge base that agents and users read and write together. Decisions, notes, and context persist across sessions.
🔐 Per-Agent Permissions
Fine-grained control per agent. Configure file write, shell commands, and network access independently.
How It Works
1. Open the app and create a space
Launch Octopal and create a new space for your project.
2. Open a project folder
Open any folder and it becomes your project. Agents live inside as .octo files.
3. Create agents and chat
Give agents roles and start chatting. @mention them directly, or let the orchestrator handle routing.
Try It Now
Free and open source. No credit card required.
🔗 GitHub: github.com/gilhyun/Octopal
🌐 Homepage: octopal.app
Top comments (2)
This solves a real pain point. Managing multiple Claude Code projects from a single dashboard is something I've been doing manually with tmux + a shell script, and it's messy.
Two features that would make this killer:
Have you thought about integrating with the /cost command output to show cumulative spend per project?
Ha, the tmux + shell script combo — that's literally what pushed me to build this. Had like 5 terminals open and kept losing track of which project was where lol.
Per-project cost tracking is def something I want to add. When you're jumping between codebases all day, you need to know where the tokens went. Parsing /cost per project shouldn't be too hard.
For the shared CLAUDE.md thing — we're actually working on a "wiki" feature that kinda does this. You set conventions at the workspace level and they flow down to all projects. So your company style guide, testing rules, etc. just cascade automatically.
Great suggestions, keep em coming!