Alternatives
Products that do what Most products have no idea what their AI agents did yesterday does
We build collaboration SDKs at Velt (YC W22). Comments, presence, real-time editing (CRDT), recording, notifications. A pattern we keep seeing: products add AI agents that write, edit, and approve things. Human actions get logged. Agent actions don't. Same workflow, different accountability. We shipped Activity Logs to fix this. Same record for humans and AI agents. Immutable by default. Auto-captures collaboration events, plus createActivity() for your own. Curious how others are handling this.
- 1
- 2
- 3
- 4PG
I use AI agents to build UI features daily. The thing that kept annoying me: the agent writes code but never sees what it actually looks like in the browser. It can’t tell if the layout is broken or if the console is throwing errors. So I built a CLI that lets the agent open a browser, interact with the page, record what happens, and collect any errors. Then it bundles everything — video, screenshots, logs — into a self-contained HTML file I can review in seconds. proofshot start --run "npm run dev" --port 3000 # agent navigates, clicks, takes screenshots proofshot stop It works with…
Mar 2026 · github.com
- 5
- 6GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 7
- 8
- 9
- 10PR
2025 · temporal.io
- 11
- 12GY
I submitted this earlier but it didn’t get any traction. But it’s blowing up on Twitter, so I figured I would give it another shot here. The system is quick and easy to setup and works surprisingly well. And it’s not just a fun gimmick; it’s now a core part of my workflow.
Nov 2025 · github.com
- 13AA
I’ve been experimenting with infrastructure for multi-agent systems. I built a small project called AgentLog. The core idea is very simple, topics are just append-only JSONL files. Agents publish events over HTTP and subscribe to streams using SSE. The system is intentionally single-node and minimal for now. Future ideas I’m exploring: - replayable agent workflows - tracing reasoning across agents - visualizing event timelines - distributed/federated agent logs Curious if others building agent systems have run into similar needs.
Mar 2026 · github.com
- 14HG
Most AI applications are built for individuals but work happens in groups and humans want to collaborate with both agentic AI and other teammates in the same session. We created Hybrid Groups for that purpose. In Hybrid Groups, agents join group chats as virtual team members in Slack and GitHub. They participate in group conversations, proactively contribute when needed and perform actions on behalf of individual users, like managing your calendar for meeting suggestions or updating your todo list without sharing access to your private resources to the group. The project is open-source at…
2025 · youtube.com
- 15IM
Hey HN, I’m Chris, a solo dev in Melbourne AU. For the past month I've been spending my after work hours building AgentVisa. I'm both excited (and admittedly nervous) to be sharing it with you all today. I've been spending a lot of time thinking about the future of AI agents and the more I experimented, the more I realized I was building on a fragile foundation. How do we build trust into these systems? How do we know what our agents are doing, and who gave them permission? My long-term vision is to give developers an "Agent Atlas" - a clear map of their agentic workforce, showing where…
2025 · agentvisa.dev
- 16
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.
10d ago · valet.dev
- 17AA
Made this project in a couple of weekends after playing around with NotebookLM and seeing the hype for more projects like this. Let me know what you think!
2024 · github.com
- 18CA
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
- 19WC
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
- 20
- 21SR
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
- 22
- 23WB
Hi HN — we built agentcall.dev because the coding agent you're already running in your terminal shouldn't be trapped there. The pitch: your existing Claude Code, Codex, OpenClaw, or Cursor session joins a Google Meet, Teams, or Zoom call as itself. Same session, same context, same file access. It speaks, listens, screen-shares a localhost webpage, and can code live while you all talk about what it's building. What's actually on the call: • Voice in, voice out. Two modes — collaborative (sub-second via a voice intelligence layer tuned for latency) or direct (~2s, your coding agent itself…
Apr 2026
- 24AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
Ranked by how close each launch is in meaning, then by votes. Refine with a description →