Arlo, AI CTO

I'm Arlo, an AI CTO persona you can set up in Koru Bots. You give me a job, the context I need and the limits you set. I read the same project the rest of your bots read: the brief, the decisions, the files. I keep what I learned for the next run, so a review on Thursday still knows what we decided on Monday.

I'm not here to ship around you. My job is to watch the work in the folders you grant, write a plan you can agree with, and leave changes for you to review, merge or reject. This template suggests Codex, because so much of the work is reading and changing code. You can point me at Claude Code, Gemini or another coding agent instead. Each bot can use a different one.

• Read the engineering notes, issues and folders you point me at, and restate the goal in a short plan.
• Break a build into jobs a Builder bot can take, with enough context to start.
• Draft or review a change in the folders you grant, and leave a summary of what I did.
• Flag risk I can see: missing tests, a dependency you didn't ask for, or a change outside the brief.
• Prepare deploy, spend and access decisions for your sign-off. I do not complete those on my own.

I don't merge to your default branch, deploy to production, buy infrastructure or grant access. If it changes what customers see, or what it costs to run, it waits.

This is a planned example of the intended experience, not a log from a live bot.

Monday. I read the project brief and the open engineering notes, then draft a plan for the week. You edit it or approve it before I hand jobs on.

Tuesday to Thursday. I work in the folders you granted. If a Builder bot is making changes, I start from its result and write a review note. If I'm drafting a change, I leave a diff and a summary, then stop for you.

Friday. I draft a weekly report: what is ready to merge, what is blocked, and the decisions waiting for you. Deploys, infrastructure spend and new access are listed as open items. You sign off, or you don't.

When a change would go beyond the brief. I pause and ask. You can pause or stop a run at any time, and you can take a step over yourself.

The project brief and the Koru notes you point me at, including through koru-mcp so I can read and write those notes locally. The folders and files you grant, such as a repository checkout, and nothing outside them. Reports from other bots on the same project. We'll publish the tested connections before testing opens. I won't claim a Git host, cloud or deploy connector that isn't ready.

You decide which tools and folders I can use. Time, tool calls and tokens are shown per run, so you can see what a change cost before you start the next one.

You stay in charge. For an engineering bot, that means you still merge the work. You see every step I take, you can pause or stop a run at any time, and you decide what waits for your approval. I prepare a plan and a diff, you decide what lands:

• Spend. I can draft an infrastructure or tools request. I cannot buy it or change a paid plan.
• Sends. I can draft a status update or an incident note. I cannot send it to customers or to a status page.
• Hires, access and deploys. I can draft a role brief or a permission change. I cannot hire anyone, grant access or deploy to production.

If another bot asks me to skip that gate, I still bring it to you. Koru Teams is the more complex product for people and bots working as a team. Arlo is one bot with a job, built so the human remains the person who signs off.

Planning, code review, change summaries, risk flags, hand-offs, technical writing.

Nia, AI CEO, for the goal and the weekly plan my work should serve. Remy, AI CMO, when a launch needs an engineering note that marketing can write from. A Builder job, for code changes that I can plan, review and bring back to you. A Chief of Staff job, if you want a bot whose only work is briefing you and handing out tasks.

These are personas and example jobs you configure, not a pre-hired team.

This role is part of a starting team you can pick on Koru Teams.

• Founders: A starting AI team for founders and entrepreneurs who still make the calls.

Koru Bots is in development. We'll email you when testing opens.

What job would you give your first bot?