Stas AI Bridge

Commented on AI Bridge · Oct 24, 2026

Thanks, good question! It depends on your setup. If your agents work in separate git worktrees, collisions are rare: each has its own copy of the repo, and you decide what merges first. If they share one checkout, each approval still comes through the Inbox, so you choose what goes first and what waits. There is also AI Assist... the built-in overseer, it can see both agents and the repo, and it can take control over both of them or multiple and help you reconcile , its ai for helping to manage other ai's essentially :)

Commented on AI Bridge · Oct 24, 2026

Hey DevHunt 👋 I built AI Bridge to solve a few of my own problems. Since Claude Code and Codex arrived, I've worked mostly in terminals. I've almost completely stopped using VS Code, except to change the odd .env file: my whole workflow shifted to investigating and approving code with agents in the terminal. The whole Cursor revolution flew over my head. I had a Cursor subscription from work, but I barely used it; I never felt I needed to look at the codebase in its entirety. If I needed something, I asked AI to find it and show me the file in the terminal. If I needed a change, I asked AI to make it, then watched and approved. 💡 Then a friend showed me a tool for managing agents, and it was my light-bulb moment: making agents easier to manage is the right idea, but that implementation didn't fit my workflow. That's when I started building AI Bridge. 😩 The pain A pile of terminal windows to manage. I'd rather have a session only for frontend and design work, without polluting its context with database queries, cluster checks or random support requests from colleagues. I wanted to group agents by department or area within a company, with my personal projects and consultancy work in the same app. 🛠 What AI Bridge does for me 🗂 Groups my agents (the real CLIs) by the job they do rather than by repo, still in a terminal view. 🗄 Lets me chat to a database and see the data directly. Before, I'd ask an agent to query it, with no proper way to see the results unless I opened phpMyAdmin or Postico. ☸️ Connects to Kubernetes clusters directly: I can see pods update, check that External Secrets, Argo or Flux has synced, or explore the cluster visually. AI can check a cluster's health quickly, but so can an experienced engineer with a good visual, and for me that's faster than asking another agent. 💬 Connects an agent to a Slack channel. When a colleague asks me a DevOps or platform question, it comes into AI Bridge and I approve it. The agent runs from my terminal with the permissions I gave it, and I approve the reply before it goes back to Slack. 🔲 Gives me the Grid when I want the same feel as zsh and my other terminals, plus everything above. 🔁 Moves Claude Code and Codex sessions between computers: with AI Bridge on both laptops, I export on one and import on the other. 👋 About me Over the last few years I've been a cloud lead, principal engineer and head of engineering, and I run my own consultancy helping clients with infrastructure, automation, compliance and internal tooling. If you work across the full stack, cloud, product and support, you'll find it helpful. I use it every day in my own job, and I'd love to hear what you'd want it to do next.