Alternatives
Products that do what Workplane – collaborative files for agents (and humans) does
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!
- 1

- 2

- 3

- 4CC
I’ve found coding agents to be great at 1/ finding everything they need across large codebases using only bash commands (grep, glob, ls, etc.) and 2/ building new things based on their findings (duh). What if, instead of a codebase, the files were all your workplace docs? There was a `Google_Drive` folder, a `Linear` folder, a `Slack` folder, and so on. Over the last week, we put together Craft to test this out. It’s an interface to a coding agent (OpenCode for model flexibility) running on a virtual machine with: 1. your company's complete knowledge base represented as…
Jan 2026
- 5

We're been seeing an explosion of agent generated artifacts get shared in companies, but with no place to put them or comment on them their utility is limited. We're building Valet to give agents the tools to collaborate with humans.
9d ago · valet.dev
- 6TA
Hi everyone! I built this because I wanted a little bit more organization around my Claude sessions, worktrees and plans while staying in the terminal and not relying on another SaaS tool. Since it's a command line tool, the added bonus is that Claude can use `td` directly. The td calendar was just a fun add-on but the Claude session stats have been pretty interesting! Let me know what you think!
Apr 2026 · github.com
- 7RM
I was tired of asking my claude code to reference my codex chats to get references to what decisions it made and why ; so I built Reference MCP It, whenever prompted establishes sessions to get direct access - been using it on my system for a bit and was super helpful so I made a repo :) Would love feedback!
Jun 2026 · github.com
- 8AL
Hello HN! I wanted to share a small MCP + web app I built to solve a problem at work. Essentially, we’ve been doing great when working with agents 1:1, but collaboration has been a struggle. E.g. when I have to collaborate with a teammate and share context or handoff work usually what I would do is create a markdown with my agent, paste in slack, then my teammate will copy and paste it to their agent and vice-versa. To make our lives easier, I built AgentCouch, a “messaging app” for agents that lets our agents chat and hand off work directly in shared rooms. Humans can also watch the…
Jul 2026 · agentcouch.dev
- 9MA
This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…
2025 · github.com
- 10SR
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
- 11CM
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…
Feb 2026 · github.com
- 12AM
Hey HN, I noticed there are 1,000+ MCP skills on GitHub with zero way for creators to charge for them. So I built Agent37. Selling Claude skills today means asking customers to download your skill, set up Claude Code on their laptops, configure MCP servers, and pray it works. No trial, no updates, often you're just handing over the source. Agent37 lets creators upload a skill, share a link, and anyone can try it instantly (no Claude account needed). Built-in Stripe, creators keep 80%. Looking for feedback on the approach. Would you use something like this?
Dec 2025 · agent37.com
- 13FF
It uses your local Claude and GitHub CLI and git worktrees, so there's nothing to configure beyond what you already have. Our AI coding workflow was a hodgepodge of scripts and ad-hoc processes, so we built this to centralize and streamline - and most importantly adapt as things change. Some cool features so far (lots more planned): 1. One click github issue to agent working on it. 2. Ratcheting mode, where it watches CI for code review comments and build failures, and automatically fixes them. Would love genuine feedback, bug reports, PRs, suggestions, etc.
Feb 2026 · github.com
- 14AA
Hey HN! We've just open-sourced Agent, our framework for running computer-use workflows across multiple apps in isolated macOS/Linux sandboxes. After launching Computer a few weeks ago, we realized many of you wanted to run complex workflows that span multiple applications. Agent builds on Computer to make this possible. It works with local Ollama models (if you're privacy-minded) or cloud providers like OpenAI, Anthropic, and others. Why we built this: We kept hitting the same problems when building multi-app AI agents - they'd break in unpredictable ways, work inconsistently across…
2025 · github.com
- 15BA
I'm building a workspace for doing focus work while also managing constant multi-tasking and context-switching that's required in a lot of roles. Currently this is done by using a notes system where we can split-screen AI chat, an object-based data table system for tracking entities, as well as viewing other documents. We can define agents directly from documents by giving instructions in plain language and then defining the trigger conditions. This helps automate workflows directly in the place where we're reading and writing content. I'm continuing to experiment with instructions and…
2025 · useportals.dev
- 16MO
Why we built it: • Claude Code: great for coding, but no video/audio support, localhost only • OpenAI SDK: single-model, no native multimedia tools • Both: no integrated DevTools for debugging agent reasoning So, we built Mix as an alternative for multimodal applications. • Native video/audio/PDF analysis tools (via Gemini for vision, Claude for reasoning) • Multi-model routing instead of single-provider lock-in • One-command Supabase setup for cloud deployment (vs localhost-only) • HTTP architecture that enables visual DevTools alongside agent workflows • Go backend: 50-80%…
Oct 2025 · github.com
- 17CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 18NO
We're open sourcing Nimbalyst, a multi-agent, visual workspace for building with Claude Code, Codex, and Opencode (alpha). It pairs parallel session management with WYSIWYG editors so you and your agents can work on the same files at the same time. The core idea: agents edit files, you edit files, and Nimbalyst makes that collaboration legible. Built-in WYSIWYG editors cover markdown, mockups, Excalidraw diagrams, data models, spreadsheets, and code (Monaco). Every edit is tracked back to the session that made it, with red/green WYSIWYG markdown diffs for review and approval. A session…
Apr 2026 · github.com
- 19UA
I've been using LLMs for long discovery and research chats (papers, repos, best practices), then distilling that into phased markdown (build plan + tests), then handing those phases to Codex/Claude to implement and test phase by phase. The annoying part was always the distillation and keeping docs and architecture current, so I built Unpack: a lightweight GitHub template plus docs structure and a few commands that turns conversations into phases/specs and keeps project docs up to date as the agent builds. It can also generate Mintlify-friendly end-user docs. There are other…
Feb 2026 · github.com
- 20GC
Hello HN, we're Andrew and Stephen from Keyboard (https://www.keyboard.dev/). After building AI tools for the past year, we recently made a YouTube video on building MCP servers and realized MCP is a total game-changer. It essentially lets AI do anything by connecting to your apps. But the deeper we dove, the clearer it became that security and privacy were complete afterthoughts. Coming from backgrounds at Okta and Stripe, this made us pretty uncomfortable. We kept seeing the same pattern: every app needs its own MCP server, each storing sensitive tokens, with minimal…
2025 · github.com
- 21OA
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…
Aug 2026 · ocean.mosaic.inc
- 22OO
One coding agent orchestrator UI for Claude and Codex, but actually feels nice. Free, open-source, MIT licensed. Why I built it: - I wanted a lightweight UI as nice as the Codex app, but without the complexity and the custom diffs on the side - I want files and diffs open straight in my editor! - And I wanted both agents - Anthropic + OpenAI — in one place How it works: - No API keys, no OAuth, no separate billing — it just uses whatever you're already logged into. So your Claude Max and ChatGPT/Codex subscriptions both work out of the box. - Talks to Claude Code via the Claude Agent…
Apr 2026 · github.com
- 23IB
Mix is an open-source, local agent for multimodal claude code. Claude code users will feel at home. - Uses ffmpeg and local apps like blender instead of clunky cloud based editors - All project data is stored plain text and native media files - absolutely no lock-in. - The backend is an HTTP server, meaning that the frontend is just one of possible clients. - - Our SDK with stdio interface (similar to claude code SDK) is launching soon.
2025 · github.com
- 24DE
I wanted a very simple way to dump prompts, links, and todo lists into my claude code and codex agents. And to work outside of the context window. This works particularly well for sharing "Projects" between Claude/ChatGPT etc. It's open source here; https://github.com/Vochsel/dump.page Anything you dump on the board becomes an llms.txt - spatially sorted implicitly and explicity sorted via connection edges. Would love HN's thoughts!
Mar 2026 · dump.page
Ranked by how close each launch is in meaning, then by votes. Refine with a description →