Coding & Development๐คclaude๐universal
AgentHydra
Every local AI coding session in one tab: Claude Code, Codex and OpenCode in a single list, with a queue you can schedule and isolated Claude Desktop instances kept apart. Local, private, MCP-native.
Quick Start
Install this Skill
npx skills add LunarWerxs/AgentHydra<div align="center"> <img alt="AgentHydra. Every local AI coding session, in one tab: many heads, one dashboard" src=".github/og-image.png" width="820" /> ### Every AI coding chat on your PC, and every Claude and Codex account, in one window [**Website**](https://agenthydra.lunarwerx.com) ยท [Download](https://github.com/LunarWerxs/AgentHydra/releases) ยท [Reference](docs/REFERENCE.md) ยท [Changelog](CHANGELOG.md) [](https://agenthydra.lunarwerx.com) [](https://github.com/LunarWerxs/AgentHydra/actions/workflows/ci.yml) [](https://github.com/LunarWerxs/AgentHydra/releases) [](LICENSE) [](https://discord.gg/PsWpeNUzhk) </div> --- AgentHydra is one local window over every AI coding session on your PC and every Claude and Codex account you use. No cloud service, no sign-up.  <sub>Screenshots use demo data.</sub> ## TL;DR - **Every chat in one sidebar:** AgentHydra's own Claude Code chats, Claude Desktop's and the CLI's, grouped by project, live while they run - **New starts from your projects:** a grid with each one's git state and open chats, the busiest first - **Dev servers built in:** start, stop and watch your projects' local servers, and open them beside the chat - **CliMayte:** hand a task's pieces to your other Claude CLI accounts, and a worker moves on when one runs out - **Where the time and money went:** cost by day, model, project and account, and what is wasting it - **Every Claude and Codex account in one table:** plan, 5-hour and weekly quota, open, quit, create - **For agents too:** the whole thing over MCP, including "which account am I, and how much is left" <details> <summary><b>Read more: what each part does</b></summary> ### Every chat, in one window - The sidebar holds AgentHydra's own Claude Code chats (composer, permission prompts, to-dos, diffs, Create PR) beside your Claude Desktop chats and CLI sessions, grouped by project. Filter by app, or keep only what is running or waiting on you. With Login sync, your other PC's chats are there too. - Codex and OpenCode conversations are listed and readable too; replying is Claude-only. - **New** opens a grid of your projects, from Project Hydra, the folders you add and wherever your chats ran, each with its git state and how many chats are open in it. A chat started in a parent folder counts for the project it actually worked in, and is filed into that project's group.  ### Dev servers, built in - The Dev servers page lists your projects' local servers: start, stop, restart, logs, errors, CPU and memory, alerts. A browser pane beside the chat opens any of them. - A folder needs no setup: it reads Claude Code's `.claude/launch.json`, or `package.json`'s dev scripts. (This was DevWebUI; it is part of AgentHydra now.) - **ChatGPT handoff** packs the task and repository into a Markdown file (common secret files left out), copies a prompt and opens ChatGPT. You review and send it yourself. - Open a raw Claude or Codex `.jsonl` in your editor, download it under its title, or copy it. ### Reply, fan out, or move a session, never headless AgentHydra never runs a chat you cannot see: every run is in a real app window. - **Reply** into a session's own desktop chat; it checks the message landed. A busy chat says so. - **Fan out** a task list across your other signed-in accounts (MCP `fan_out`), one visible chat each, and steer them with `fan_out_send`. - **Import** a session into a desktop app to continue it by hand. - **Move** a chat to another account with `move_chat`, or several with `move_chats`. It keeps its history ([Moving chats between accounts](docs/MOVING-CHATS-BETWEEN-ACCOUNTS.md)). The old run queue stays as a read-only record. Starting a new headless run is refused on purpose. ### CliMayte: hand a task's pieces to your CLI accounts - A chat keeps the plan and hands each piece to a Claude Code CLI session on one of your accounts. When an account nears its limit, the worker moves to another and carries on. - No console windows, but nothing hidden: every worker is readable and steerable in the CliMayte view, and its transcript is a normal session. - **Quick add:** type an email, sig ... (truncated)
Repository
46stars
3forks
Details
Related Skills
More coding & development skills you might like
Reticle
Coding & DevelopmentAI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications.
๐คclaude๐universal
1.2k
190
View
agentscope-java
Coding & DevelopmentExpert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or Java agent development. Specializes in non-blocking code, tool integration, hooks, pipelines, and production-ready agent applications.
๐universal
6.0k
1.5k
View
ospec
Coding & DevelopmentDocument-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
โจgemini๐คclaude๐ฌgpt๐universal
524
34
View
misakanet-failure-memory
Coding & Development๐ A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | https://misakanet.org
๐คclaudeโจ๏ธcursor๐universal
424
158
View