Skip to main content

Koru Bots

In development

Your team of bots, working 24x7 on your AI subscription.

Each bot gets a job, the context it needs and the limits you set. They hand work to each other and report back, running on Claude Code, Codex, Gemini and other coding agents you already pay for.

We'll send a welcome email with your personal share link.

We'll email you when testing opens.

Need bots working together? See Koru Teams
The Bots view of the Koru app, early build. Research Scout, running on this device, reports its weekly digest run: it added three sections to the Weekly Digest note and created a follow-up task, with Review changes and Undo run buttons. Asked to skip hardware threads from now on, it says it updated its instructions. The side panel shows where it runs, this device or Koru Cloud, its Monday 8:00 AM routine and what it can access.
Early build, in development.

Bots with a job, not another chat window.

Examples

  • Scout

    Researches and hands findings on.

  • Writer

    Turns findings into drafts.

  • Builder

    Makes code changes with Claude Code.

  • Chief of Staff

    Briefs you and hands out the work.

Name the job, give it the brief once. It keeps what it learned for the next run.

The Bots view of the Koru app on a first visit, early build: no bots yet and the line 'A bot is a chat that works on its own'. It runs on this device or in Koru Cloud, and three bots to start from are offered: Research Scout, Inbox Triage and Spec Reviewer, with New bot from scratch below.
Early build, in development.

Meet your team of bots (coming soon).

These are personas you can configure: a name, a role, a runtime and the limits you set. They are not hired people, and they do not sign off for you. Each one can run on Claude Code, Codex, Gemini or another coding agent you already pay for. Koru Bots is in development.

Want a different role? Name the job, give it the brief once. Or join the waitlist and tell us what you would set up first.

They share what they know.

Every bot reads the same project: the brief, the decisions, the files. When one finishes, the next starts from its result, not from zero.

A design of the planned Koru app: a project run named earthy-swallow, with the goal of summarising the September Apple keynote. Two bots at work: Scout, done, which read the brief, searched the web and handed its findings to Writer, which is writing section 3 of 5. Beside them the run's context, its time, tool calls and tokens, and two files it saved.
Concept preview: planned experience. Not a screenshot.

Runs on the subscription you have.

Bring Claude Code, Codex, Gemini and other coding agents. Each bot can use a different one.

  • Claude
  • Codex
  • Gemini
  • Grok
  • GitHub Copilot
  • OpenCode
  • Antigravity
  • Kimi
  • Qwen Code

On your computer, or always on.

Run them on your own computer, or give them their own always-on machine (paid add-on, coming soon).

You stay in charge.

  • See every step each bot takes.
  • Pause or stop a run at any time.
  • Decide which tools and folders a bot can use, and what waits for your approval.

Time, tool calls and tokens are shown per run.

Open source, private by design.

The Koru app is open source under MPL-2.0, built in Rust, and works offline.

Questions

Can I use Koru Bots today?

Not yet. We're building it now. Join the waitlist to hear when testing opens.

Can I use my own AI subscription?

That's the plan: each bot runs on the subscription you bring, for Claude Code, Codex, Gemini and other coding agents. We'll publish the tested connections before testing opens.

What will it cost?

We haven't announced pricing yet.

What job would you give your first bot?

We'll send a welcome email with your personal share link.

Privacy choices

Choose which optional tools Koru may use on this site. Your choice is saved in a cookie in this browser for 12 months. Privacy policy

Privacy choices

Keep you signed in, protect forms and remember your language and this choice.

Always on

PostHog and Google Analytics 4 measure page views and actions such as downloads, using cookies or local storage.

PostHog records how pages are used, with form inputs masked and private pages excluded. Needs Analytics.

Ahrefs Web Analytics measures visits and where they come from, and Google Ads measures whether our ads led to a visit or download.