Name: bise
Author: Gabriel Vergnaud

why

you didn't become an engineer
to babysit robots.

today you started five things. you watched output scroll. you answered "should i continue?" eleven times.

two agents edited the same file, and you found out from the red tests. you pasted the same context into three tabs. you had a great idea at 2pm, and you let it go, because one more tab was one too many.

at 6pm you'd shipped more than ever, and you felt like you did nothing.

you can build a whole product on your own now.
you just need your head back.

how

one thread. a whole team.

you talk to main, bise's main agent. main splits your ideas into jobs and runs the other agents.

you "add dark mode. and the api client moves to v3." │ ▼ :* main always listening. knows everything going on in the repo. │ ├── ∿ theme the dark colors, in one place ├── ∿ toggle the switch in settings, remembered per user ├── ∿ docs new screenshots, a changelog line └── ∿ api-v3 the client upgrade. unrelated, so it runs too.

1one thread per repoone thread to talk to. peek into any agent when you feel like itno tabs to juggle, no "wait, which session was that?". main knows everything going on in the repo, even what you did last month.
2main is always listeningthe team is busy. main never isask, add a thing, change your mind while the agents work. main answers right away.
3a team that runs itselfthey talk behind your back. in a good wayagents message each other before they collide. when one needs its own copy of the repo, it makes a worktree and cleans it up after. each one commits its own work.
4forget there are agentsno yaml was harmed.no roles, no graph, no config. bise has opinions, so you don't need any. you just dump your ideas in the thread.

what it feels like

kiss your backlog goodbye.

ten things you'll notice in the first hour

talk whenever. you never wait

say the next thing while the last one runs. your composer is never locked.

agents sync on their own

every agent can talk to every other one. they ask, share and hand off quietly, folded out of your way.

all your MCPs. all your skills. always on

GitHub, Linear, Sentry, Slack, your docs, your database: connect as many MCP servers as you want, and never pick which ones to turn on. bise calls tools through code, so a hundred servers don't fill its context.

only the real decisions reach you

one card, a couple of choices, one key. then back to what you were doing.

you're not the router

main answers the obvious questions itself, the way you would, and tells you why.

talk to any agent, anytime

⌥ + a number, or @name. ask it why, push it, then go back to main. nobody has to stop.

change your mind mid-run

a correction lands in the running agent. ✓ it got it, ✓✓ it read it.

nothing gets dropped

when an agent stops half-way, main picks the work back up from where it was.

worktrees, only when they help

agents share your folder. when one really needs isolation, it makes a worktree, and cleans it up after.

bring your Agent Plugins

skills, MCP servers, hooks: plugins in the Agent Plugins format load as they are, from ~/.agents/plugins or your repo. Vibe plugins too.

and so much more

the small things add up

∿your token bill can relax · bise starts an agent when a job needs one. that's the whole rule. there's no committee of agents reviewing each other in circles.
✓it's quiet. open it up whenever · what matters to you shows. the rest is folded, never deleted: every message between agents, every tool call, every script, in full. ctrl+o opens it all.
●or just talk · turn on /voice, press ctrl+r, say it.
▣show it a screenshot · paste it with ctrl+v or drag it in. an image is one chip in your text.
❝ask about anything on screen · select a few lines in the history and start typing: they come along as a quote.
·a model per agent · the big one for the hard job, a fast one for the chores. /model and /reasoning.
$a real shell, one key away · ctrl+` opens a terminal in your repo. it keeps running while hidden.
⌃hold ctrl to see the shortcuts · each one shows up where it works. in Ghostty and kitty.
▦tables that fit · markdown tables are drawn to the width of your terminal, and wrap when they must.
♡your terminal · your colors, light or dark, text at a reading width.

questions

i already have Claude Code
keep your models, MCP servers and skills. bise changes how you work with them: one thread, and a team behind it.

won't the agents step on each other?
they tell each other what they touch before they touch it. worktrees only when one needs its own copy, cleaned up after.

how many agents can i run?
as many as you want. the real limits are your tokens, your budget and your provider.

which models?
bring your own key. the list is coming.

do i need to learn anything?
four words: you, main, agents, cards. main is the one you talk to. the rest you pick up in the first hour.

open source?
yes, under Apache-2.0. read it, fork it, send a :*.

made by a human. shipped with bise

hi, i'm Gabriel

i build coding agents for a living. i'm one of the people behind Mistral's agent tools, like Vibe.

agents made me faster. they also made my days feel empty. i was switching tabs, answering "should i continue?", pasting context around. i shipped more than ever and i didn't enjoy it.

so i built the tool i wanted: one thread, a team behind it, and me in flow. most of bise was built with bise.

i want everyone to ship like a team of a hundred, and to love building again. bise is open source and indie. i read every issue.

— Gabriel Vergnaud · GitHub

this is what flow looks like

you didn't become an engineerto babysit robots.