Alternatives
Products that do what Ocean – All your team's agent sessions in one place does
I spend a lot of time in Claude Code and Codex with my friend. We kept losing the context behind changes because every agent session lived on one person's laptop, and by the time code made it into a PR, all the reasoning was gone. We tried commits, PRs, and docs, but they only really capture the end result, so we built a tool to keep all of our agent sessions in one searchable place. Now we (and our agents) can check out anyone's session and ask things like "what was Alex working on yesterday?" It's also quite helpful in recovering the context behind a change days or weeks later. Ocean works…
- 1
- 2AO
Hi! I’m Nathan: an ML Engineer at Mozilla.ai: I built agent-of-empires (aoe): a CLI application to help you manage all of your running Claude Code/Opencode sessions and know when they are waiting for you. - Written in rust and relies on tmux for security and reliability - Monitors state of cli sessions to tell you when an agent is running vs idle vs waiting for your input - Manage sessions by naming them, grouping them, configuring profiles for various settings I'm passionate about getting self-hosted open-weight LLMs to be valid options to compete with proprietary closed models. One…
Jan 2026 · github.com
- 3SC
I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…
Dec 2025 · github.com
- 4
- 5
- 6
- 7
- 8
- 9
- 102C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 11SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 12
- 13
- 14CF
Hi everyone! Hope you had a great day so far, and maybe its about to get just a little bit better (thanks Winter ;) So I had way to many terminal windows flying about when using Claude, and kept losing track of which terminal / session / project im in right now. So I built a solution for that, presented it to my team, and now we're using our new tool all the time, and developing it to be the most helpful agents organization tool we can think of. Unfortunatelly, Claude Code only for now, will do Codex soon tho. What it does for you: Main features: - Overview of your projects, with…
Aug 2026 · episko.dev
- 15
Helping Agents and Human Orchesterators read the same notes.
Mar 2026
- 16IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 17SP
Hey HN, My cofounder and I have gotten tired of CC ignoring our markdown files so we spent 4 days and built a plugin that automatically steers CC based on our previous sessions. The problem is usually post plan-mode. What we've tried: Heavily use plan mode (works great) CLAUDE.md, AGENTS.md, MEMORY.md Local context folder (upkeep is a pain) Cursor rules (for Cursor) claude-mem (OSS) -> does session continuity, not steering We use fusion search to find your CC steering corrections. - user prompt embeddings + bm25 - correction embeddings + bm25 - time decay - target query embeddings -…
Mar 2026 · gopeek.ai
- 18PC
Hi HN, I'm Rob. Contextify indexes every Claude Code and Codex session on your machine into one local, searchable database. The current session, in either tool, can search all of it: /total-recall in Claude Code, $total-recall in Codex. Demo: https://www.youtube.com/watch?v=FvrvRGp4C9M | Mac app: https://contextify.sh (App Store or DMG) | Linux: CLI with a one-line installer, same search. No signup. I split my work between Claude Code and Codex. When I burn through rate limits on one, I switch to the other, and new models keep leapfrogging each other, so the…
Jul 2026 · contextify.sh
- 19SI
Claude Code is amazing for individuals but terrible for teams. I spent the last six months building my perfect mix of MCP servers, subagents, commands and skills. Claude Code writes 100% of the code now, but sharing this with my team? Painful. 1. Blog posts and workshops don't work (and don't scale) 2. Committing tools to N repos means N PRs. A tool changes? N more PRs. 3. Same tools, different files or folders for each AI assistant; not everyone uses Claude Code It is like 1999 all over again; FTPing files up to prod and versioning with ".bak" suffixes. So I built sx. It is your team's…
Jan 2026 · github.com
- 20AS
Hi HN, AgentBox is an SDK for running coding agents (Claude Code, Codex, OpenCode) inside sandboxes (Docker, E2B, Modal, Daytona, Vercel). One API. Swap the agent or the sandbox and your code doesn't change. Think of it as what the AI SDK did for LLMs, but for agent + runtime. Most wrappers call agents in non interactive mode (claude --print, codex exec). AgentBox instead boots each agent's native server inside the sandbox (Codex app-server over JSON-RPC, OpenCode serve over HTTP/SSE, Claude Code's SDK WebSocket transport) and drives it from the host, behaving like an interactive…
Apr 2026 · github.com
- 21WC
A friend and I built this as a side project to help us collaborate on files with our agents. Claude / Codex kept outputting .md and .html files which are great until we needed to share them, so we built this small website to help with that. Agent can either use an HTTP + Skill or an MCP which also uses MCP Apps to add widgets to Claude Desktop / Mobile chat. Would love any feedback and hopefully this helps someone else as it did us!
Jun 2026 · workplane.co
- 22OA
We were both genuinely impressed by Claude Code after it helped each of us fix nasty CI problems overnight. Doing those fixes manually would have taken days. After that experience, we each found ourselves struggling through Ctrl+Tab through multiple Claude Code windows in our terminals. While we enjoyed having agents working for us in parallel, context switching and cycling through each terminal tab was a real pain. So we thought: Can we design a TUI dashboard that manages a large swarm of agents in one place? Even better, can agents manage agents hierarchically, like how companies work?…
May 2026 · omar.tech
- 23SS
Hola HN! Long time lurker, sometimes commentor, first time poster here. I’ve been working alongside my two co-founders and a few colleagues on a project I’m excited (and a little nervous) to share with you all! Like many of us, I’ve lived a tortured existence with AI coding (is it vibes?) over the past few months - I think November was a big moment with this. But, one thing I’ve noticed after building orchestration layer after orchestration layer is that the thing I always came back to was “what the hell is Claude Code actually doing?” Perhaps it’s because of the time Claude Code got…
Jun 2026 · backplanes.com
- 24TA
Hey HN, I think session transcripts written by coding agents like Claude Code and Codex are very interesting because they offer a detailed window into how work gets shipped. You can see the sequence of decisions that resulted in the final PR, what the agent got wrong, tools used etc. So I built a cli that analyzes these sessions and provides a local dashboard that shows what each session shipped (PRs, features), how much each PR cost, and recommendations for more effective usage. Concretely, it enriches each session with: - Outcome links: merged PRs, features shipped, files changed -…
Jul 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →