An audio-visual interface to your agents.
Bicycle is a Mac app. Watch the demo here, then send yourself the link.
Works with and more
An audio-visual interface to your agents.
It raises the bandwidth between you and your agents. You talk and sketch to them, and you see and hear what they did.
- Talk to your agents.
- Sketch or write what you want, like you would for a colleague.
- Hear and see what they did and what they understood.
- Get work done across your apps without leaving the screen.
Bicycle isn't out yet. Leave your email and we'll write when it's ready.
Bandwidth is how much you and your agents understand of each other per minute. Most work with agents runs through the same four steps. Chat agents reach your apps through MCP too. What slows you down is the format: one long thread of text you scroll back through.
1Find out
It can reach your apps, but the answer comes back as a long reply you scroll through.
What it found lands as islands, side by side.
2Understand
It writes a wall of explanation. It can't walk you through it while you watch.
It talks you through it step by step while the board draws and highlights the part it's on. Interrupt and point any time.
3Brainstorm
Earlier ideas scroll out of view, so you quote them back.
Options stay on the board. Point at one and talk it through.
4Push
The result is one more message further down. You scroll and read to check it.
The result lands on the island it came from, showing what changed. It asks before anything you can't undo.
Tap one to watch it on the board. The data in the runs is invented, except the sanctions facts, which are from the US Treasury.
More you could ask
Or tap the mic and ask in your own words.
- You ask out loud: why did signups drop since Tuesday?
- The funnel from PostHog, the deploy from GitHub and a phone screenshot land side by side.
- Claude Code and Codex each post a hypothesis.
- You point at Codex's hypothesis and ask why that one.
- The answer lands on that card, in place.
- You sketch the fix: two boxes and an arrow.
- Bicycle says back what it understood.
- Claude Code writes the patch and a test, and runs the tests.
- The change lands grouped by what it does, with one risk flagged.
- You point at the risk and ask. The answer lands on that row.
- Before it opens the pull request, it asks for your OK.
- You ask out loud what customers are stuck on.
- Themes from call notes and support land with quotes, ranked by mentions and revenue at risk.
- The activation funnel sits beside them. The biggest drop is at import.
- You point at the top theme and ask which accounts.
- You talk through two options.
- You sketch the simpler one.
- Bicycle says the plan back.
- A one-page spec is drafted from the plan.
- Three tickets are drafted under it.
- Before it creates them in Linear, it asks for your OK.
- You ask for this month's investor update.
- Revenue from Stripe, active teams from PostHog, burn from your accounting and what shipped land as tiles.
- You point at MRR and ask why net new is down.
- The two churned accounts appear, with the reasons.
- You ask for a lowlights paragraph that says what you are doing about it.
- You point at one sentence and ask for it softer. Only that sentence changes.
- The whole update is drafted from what you agreed.
- Before it sends anything, it asks for your OK.
- You ask: walk me through breadth-first search.
- It starts at A: everything one step away comes before anything two steps away.
- Level by level, nodes light up in the order they come out of the queue.
- You interrupt: why a queue and not a stack?
- The island amends in place: a side panel shows the order a stack gives.
- You ask when you would use it.
- One line back, and the shortest path from A to H lights up.
Illustrative portfolio. Not financial advice.
Source: U.S. Treasury press release, 15 Oct 2026 and OFAC's list update.
- You ask how Thursday's sanctions affect your portfolio.
- The Treasury action lands next to your portfolio.
- Holdings with any plausible link are marked. Most of the portfolio has none.
Illustrative portfolio. Not financial advice.
- Bicycle walks the chain link by link while the board draws it.
- It marks what the chain touches in your portfolio, and what it doesn't.
- You point at one link and ask how big it is. The answer lands on that link.
Illustrative portfolio. Not financial advice.
- Three options land on the board.
- You point at one and talk it through.
- Bicycle says back what it understood.
Illustrative portfolio. Not financial advice.
- The alert is set and a note to your adviser is drafted.
- Before it sends anything, it asks for your OK.
Your mind doesn't have folders, tabs and apps for your thoughts. On a board, your questions, the answers and the agents' work sit side by side, and you can point at any of it.
Tap a question. The answer lands on this board and the view moves to it. You can also type your own in the bar below.
Start here
Try one
Before you trust it
About us
One agent run, shown three ways. The run is an invented example: an agent was asked to make failed uploads retry.
In a terminal
$ agent "make failed uploads retry" ● Reading src/upload/client.ts (212 lines) ● Reading src/upload/queue.ts (148 lines) ● Searching for "retry" in src/ · 9 matches ● Thinking The client gives up after the first network error. queue.ts has a backoff helper that nothing calls. ● Editing src/upload/client.ts @@ -88,7 +88,12 @@ send(chunk) - const res = await fetch(url, opts) + const res = await withBackoff( + () => fetch(url, opts), { + tries: 3, baseMs: 2000, + }) ● Editing src/upload/queue.ts ● Running npm test -- upload PASS upload/client.test.ts (14) PASS upload/queue.test.ts (9) FAIL upload/resume.test.ts ✕ resumes after reconnect expected chunk 4, got chunk 1 ● Reading src/upload/resume.ts (96 lines) ● Editing src/upload/resume.ts - offset = 0 + offset = state.lastAcked + 1 ● Running npm test -- upload Tests: 24 passed, 24 total ✓ Done. 3 files changed, +41 −6.
To find the line that mattersscroll 140 lines
A chat app (like the Claude or Codex apps)
I'll start by looking at how uploads are sent and where errors are handled.
The client gives up after the first network error. There is a backoff helper in queue.ts that nothing calls, so I wrapped the fetch in it:
- const res = await fetch(url, opts)
+ const res = await withBackoff(
+ () => fetch(url, opts), {
+ tries: 3, baseMs: 2000,
+ })
I also exported the helper from queue.ts so the client can import it. Next I'll run the upload tests.
Most tests passed, but resume.test.ts failed: a resumed upload restarted at chunk 1 instead of chunk 4. I changed the offset in resume.ts to continue from the last acknowledged chunk and ran the tests again.
Yes. All 24 tests pass. 3 files changed, +41 −6. Let me know if you'd like different retry timing or jitter between attempts.
To find the line that mattersscroll 3 replies, open the tool calls
On a board
Failed uploads now retry 3 times, waiting 2, 4 and 8 seconds. A resumed upload keeps its place.
- const res = await fetch(url, opts)+ const res = await withBackoff(+ () => fetch(url, opts), {+ tries: 3, baseMs: 2000,+ })client.ts, queue.ts, resume.ts · +41 −6
24 of 24 pass. One failed on the way: a resumed upload restarted at chunk 1. Fixed in resume.ts.
To find the line that mattersit's highlighted
You see the summary, the change and the result, and you can point at any part and ask.
A Wider Channel
Each era of computing widened the channel between people and computers, from punched cards to a screen you can point at.
Now agents work faster than we can follow, so understanding what they did is the bottleneck, and Bicycle widens the channel again on the devices you already own.
- You sketch the flow: two boxes and an arrow.
- You scribble a note on the part to change.
- Bicycle says what it understood and asks before handing it off.
- The plan lands beside your sketch, which is marked understood.
- You highlight a few words in the middle of a paragraph.
- You ask about them out loud.
- That paragraph changes in place. The rest of the island stays put.
- You ask out loud.
- Bicycle answers in a sentence, and the options land on the board.
- You point at one row and say "change that part".
- That row changes in place. The rest stays put.
- An agent's pull request lands on the board as an island.
- You point at one hunk.
- You ask why.
- The answer lands in place, under that hunk.
- You ask why a test failed.
- An agent investigates on your Mac.
- The failing check, the cause and the fix land as one island.
- Before and after, and the tests pass again.
A project folder per board
Each board has a project folder. Work for that board happens in that folder.
You pick the agent
You choose which agent on your Mac does the work for a board. It works with Claude Code, plus Codex, OpenCode and Pi.
It reports back
The agent works in the background while you keep talking. When it finishes, it reports back to the same board, and you can ask it what it did and why.
Your terminal agent, on a board
Bicycle does not replace your coding agent. It hands work to the agents already on your Mac: Claude Code, plus Codex, OpenCode and Pi. It puts what they did on a board you can talk to and point at. Several agents can report back to one board.
When it gets it wrong
You can ask the agent what it did and why, tell it what to fix, or ask Bicycle to stop the job.
Connected apps
Bicycle connects to the apps your agents already reach through MCP, the common protocol for connecting tools to agents. Settings list the connected apps for each agent.
On your Mac
Speech can run on your Mac. You choose on-device speech or our cloud in settings.
Our cloud
If you choose the cloud, your audio and text go to our servers to be transcribed and answered.
Your provider
Answers can use a subscription you already have, an API key, or an endpoint you run yourself. Requests go to the one you choose.
Training on your data
A data policy, including whether anything is used for training, has not been announced. Join the waitlist to hear first.
This page
When live voice is on, what you say or type here is sent to our servers to transcribe and answer, then discarded. We keep a count of your questions for a day so the demo stays free. Tapping a suggested question plays a recorded answer and sends nothing. When live voice is off, typed questions are matched in your browser. Your email is sent only if you join the waitlist.
Who is it for?
It is built first for people who write software and work with coding agents. It supports Claude Code, plus Codex, OpenCode and Pi. The plan is to widen from there.
Why voice?
You can talk while you look at the board and while agents work, with no window to switch to. The voice keeps it short and the board holds the detail.
What is an agent?
A program that does real work on its own for a while. It can read a codebase, fix a bug, search the web, draft a plan or file a ticket.
How fast is it?
Running speech on the Mac's own hardware cut the time to first speech from about 700 milliseconds to about 185. Low latency is the first rule every design choice is judged against.
Does it remember my project?
Yes. Each project keeps a knowledge base: notes about the project, its files, and the work agents did for it. When you ask about earlier work, the voice looks it up there and says where the answer came from.
Is it a plugin?
No. Bicycle is a native Mac app. Being native lets speech run on the Mac's own hardware, which keeps replies quick.
Which Macs does it support?
A Mac with Apple Silicon running macOS 15 or later. An M1 with 8 GB of RAM runs it. A phone app is next.
Do I have to talk out loud?
No. You can type any turn instead of saying it. A typed turn gets the same answers, the same board and the same agents as a spoken one.
Is it open source?
That has not been announced. Join the waitlist to hear first.
When is it out?
A release date has not been announced. Join the waitlist to hear first.
What does it cost?
We're still working out pricing.
Who is building it?
The team isn't named on this page yet. Hiring and funding have their own answers: ·
Engineering
Bicycle is built for engineering first. An agent can build a feature and open a pull request. Before you merge it, you need to know how it fits into the rest of the system and how you checked that it does what you asked. When something breaks, you need enough understanding to find the cause.
Marketing
AI can make a product animation. A person still has to judge whether anyone will want to watch it. That takes a feel for pacing, music and what holds a viewer's attention.
Sales
AI can send outreach to thousands of people. A large enterprise client needs a personal approach that shows the problem your product solves for them. To automate outreach well, you first need to know what great outreach looks like.
The same need
The same need for understanding shows up in each field. AI can help you build that understanding too, and how you get it matters less than having it. Bicycle is one way to get it fast. Talk the work through, see it laid out, and point at the part you don't follow.
What will it cost?
We're still working out pricing. Join the waitlist and you'll be the first to know.
Are you hiring?
We're not hiring at the moment. Follow us on X and LinkedIn to hear when that changes.
One turn, from your voice to the board, and the model behind each step.
Speech recognition (ASR)
It depends on where you are: an Indic model or a Western one. It keeps changing as better ones come out.
Decisions: Jev
Our own decision model. On each turn it picks what happens: answer by voice, put an island on the board, change one in place, or hand the work to an agent.
Language model: Qwen
It writes the answers, unless you choose your own provider.
Speech output (TTS): Qwen
It speaks the reply.
Around them
A native Mac app. The coding agents on your Mac: Claude Code, plus Codex, OpenCode and Pi. MCP to connect the apps your agents already use.
In the app
Right now, nothing. When we add tracking, it will be usage only, such as how much you use it in a day.
Are you funded?
It'll be announced soon. Follow our socials.
Loved by people who've worked at
- Amazon
- Cisco
- Apple
- Neuralink
- HighLevel
“Useful for quick questions to Claude.”
“A perfect brainstorming partner.”
“It's removed the need for switching between apps, in the most intuitive way I've seen.”
“I've even replaced Wispr. I compose all my blogs here.”
From early users.