chernistry's profile on Product Hunt

All activity

1d ago

Most AI coding tools give you one agent, one task, one answer. Bernstein gives you many. Set a goal. Bernstein breaks it into tasks, spawns Claude Code, Codex CLI, and Gemini CLI in parallel, verifies every result with your tests, and commits what passes. You come back to working code. Zero LLM tokens on coordination — the orchestrator is pure Python. No framework to learn. No vendor lock-in. Mix models in one run.

BernsteinSpawn parallel AI agents. Ship tested code.

chernistrystarted a discussion

2d ago

Hot take: single-agent coding tools are the new FTP

Using one AI agent at a time in 2026 feels like deploying via FTP in 2015. It works, but you're leaving 80% of the throughput on the table. I've been running 5-12 agents in parallel for the past month. The productivity difference isn't incremental - it's a step change. One agent on auth, one on tests, one on docs, one on API endpoints. All at the same time. The hard part isn't running them....

chernistrystarted a discussion

2d ago

I ran 12 AI agents for 47 hours straight. Here's what broke (and what shipped).

Hey Product Hunt! I'm Alex, maker of Bernstein. Last month I ran 12 AI coding agents on a single laptop for 47 hours - Claude Code, Codex CLI, Gemini CLI working in parallel. 737 tickets closed. 826 commits. 15.7 tickets per hour. Everything that could go wrong did: merge conflicts, context drift, runaway token costs, agents overwriting each other's work, worktrees missing node_modules, port...

chernistryleft a comment

2d ago

I built Bernstein because I was tired of babysitting AI agents one at a time. Claude Code is great. Codex CLI is great. Gemini CLI is great. But you can only talk to one at a time — watch it work, wait, then start the next task. Meanwhile you're the bottleneck. The insight: agents don't need to talk to each other to work in parallel. Give each one a clear task, a fresh git worktree, and a test...

BernsteinSpawn parallel AI agents. Ship tested code.