bise :*
a multi-agent harness, made for humans.
meet your team lead.
you stay in flow, i run the agents.
$ curl -fsSL bise.dev/install | shcopy
switching from Claude Code?
why
you didn't become an engineer
to babysit robots.
you shipped more than ever today. your brain is fried 💀
should i
continue?yes, continueyou said "yes, continue" eleven times. you pasted the same context into three tabs. you forgot what tab 3 was for.
that great idea you had at 2pm? gone.
that's agent fatigue.
it doesn't have to be like this.
the problem
seven agents.
all of them need you.
every session waits for you. you're the router, the memory, and the merge tool. you ship a lot, but you never get to think.
meet bise /beez/ · french, n.
1. a quick kiss on the cheek :*
2. a brisk north wind
3. a terminal where multi-agent coding is painlessthis one
how
one thread. a whole team.
main is your team lead. it splits your ideas into jobs and runs the other agents.
you → maindark mode please. also the csv export crashes on emoji 😭
:* mainalways listening · knows the whole repo
∿ themedark colors, in one place
∿ togglea switch in settings
∿ docsfresh screenshots
∿ emoji-csvunrelated, so it runs too
- 1no sessions to find againpeek 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.
kiss your backlog goodbye
the models grew up. you can stop babysitting
twelve things you'll notice in the first hour
the team runs itself
hand it something huge
give main a big goal. it splits it into jobs, runs the agents, restarts the ones that stop half-way, and keeps going until it's done.
worktrees? don't think about it
agents share your folder. when one needs its own copy, it makes a worktree, works there and cleans it up after. no branch to name, no folder to delete, nothing to keep in your head.
your head stays yours
main is always there
main gives the heavy work to the agents, so it's never busy. ask it anything, add one more thing, change your mind: it answers right away, and no job stops.
zen mode while you type
start typing and everything else fades: the agents, the counts, the chatter. just you and your words. send it and it all comes back. what the agents said to each other stays folded, ctrl+o opens it.
hands off the keyboard
talk to it. it talks back
press ctrl+r twice and just talk to main. it answers out loud while the agents keep working, and blows you a kiss when it's done. /voice picks the model, the voice and the language.
it can use your browser
agents open pages in their own tab group, in the background, with your logins: they read, click, fill forms and take screenshots. never your screen, never your tab. Mac apps too. off until /computer-use.
no more "yes, continue"
you're not the router
main answers the agents for you: the obvious questions, the way you would, and it tells you why. only the real decisions reach you.
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.
every tool you have
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.
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.
you're still the boss
talk to any agent, anytime
⌥ + a number, or @name. ask it why, push it, then go back to main. nobody has to stop.
fits your PR flow
in a repo that takes pull requests, every change gets its own branch and its own PR, then goes through your usual flow: CI, review bots, teammates. the panel shows where each one stands.
and so much more
polished down to the last character
hundreds of tiny details. you'll feel them before you see them.
you fix the typo in the footer :* done, i did it myself. too small for an agent. 0 agents started
your token bill can relaxbise starts an agent when a job needs one. that's the whole rule. there's no committee of agents reviewing each other in circles.
╭ attached ─────────────────────╮ │ ▣ 1 cart.png 1440×900 │ ╰───────────────────────────────╯ it hides the buy button ▣ 1
show it a screenshotpaste it with ctrl+v or drag it in. an image is one chip in your text.
● listening ▂▅▃▆▂ and make the button pink ctrl+r to stop
or just talkturn on /voice, press ctrl+r, say it.
:* perf is done. signup went from 4.1 s to 0.9 s on a phone ❝ 1 what made the difference?
ask about anything on screenselect a few lines in the history and start typing: they come along as a quote.
:* main opus·hi ∿ perf opus·hi ∿ cookies haiku·lo ∿ release haiku·lo
a model per agentthe big one for the hard job, a fast one for the chores. /model and /reasoning.
$ npm test ✓ 142 passed (3.1 s) $ ctrl+` hides it. it keeps running
a real shell, one key awayctrl+` opens a terminal in your repo. it keeps running while hidden.
you /restart bise v2026.10.3 → v2026.10.4 ∿ perf ∿ dark-mode ∿ cookies back to work at once
restart whenever you likeupdate to the latest version mid-work, or quit and come back tomorrow. no work is ever lost: your agents resume right away, and your thread, your draft and your queue come back too.
$ bend PROOF.bend ✓ no message lost ✓ none delivered twice ✓ a restart = the same state ✓ nothing waits forever ALL PROOFS CHECK
agent communication is proven correctwe have the proof, thanks to Bend, a language built for the LLM era. no message lost, none sent twice.
bise :* ∿ dark-mode ✓ cookies
bise :* ∿ dark-mode ✓ cookies
your terminalyour colors, light or dark, text at a reading width.
give it a try
one line to install.
then just talk.
- 1install it
$ curl -fsSL bise.dev/install | shcopy
- 2start it in the repo you want to work on:
cd your-repo && bise - 3pick a theme, paste a key. then say what's on your mind.
runs on macOS, Apple silicon and Intel. linux soon. windows later.
you need git, and an API key: Anthropic, OpenAI, Mistral and more. a Claude or ChatGPT subscription isn't a key.
coming from Claude Code? . it installs bise and brings over your key, model, skills and MCP servers · see the full prompt ↗
later bise update to stay current, bise doctor if something feels off, bise uninstall to leave.
questions
but i already have Claude Code / Codex / Vibe
keep your models, MCP servers and skills. bise changes how you work with them: you talk to a team lead instead of juggling sessions.
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.
does it ask before running a command?
by default, no: that's yolo, everything runs. shift+tab switches to auto: safe commands just run, risky ones ask you first in your inbox, and it all runs in a macOS sandbox.
will a single thread scale to a project as complex as mine?
yes. main doesn't carry your code: the agents do the reading, each one with a fresh context. main keeps the plan and the reports, so the thread stays light. when it gets long, it compacts and keeps going. tested on a repo with millions of lines of code.
won't my context overflow? i don't want to live in the dumb zone
no need to overthink it. when a thread gets long, bise compacts it. the latest models are trained for that and they keep their trajectory. your thread just keeps going.
do i need a memory system?
nope. compaction carries the thread, and any agent can go back and read the full history: every message, every tool call. nothing gets lost.
how many agents can i run?
as many as you want. the real limits are your tokens, your budget and your provider.
what does it run on?
macOS for now, Apple silicon and Intel. linux is next. windows later, maybe through WSL first. you need git, and that's about it.
which models?
bring your own key: Anthropic, OpenAI, Mistral and more. the first run lists every provider.
do i need to learn anything?
four words: you, main, agents, inbox. 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.
agents made me faster. they also sometimes made my days feel empty. i was switching tabs, answering "should i continue?", pasting context around. i shipped more than ever and yet, i didn't enjoy it.
so i built the tool i wanted: a team lead to talk to, 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 :*
— Gabriel Vergnaud · @gvergnaud on GitHub · @GabrielVergnaud on X
:*
ideas in. little kisses out. also pull requests.
$ curl -fsSL bise.dev/install | shcopy
switching from Claude Code?
next, maybe
want a desktop app?
the same bise, in a window. your repos in a sidebar, one thread each. the agents on the right. a notification only when something needs you. i drew the screens. if enough of you want it, i'll build it.