Koda Agents

The two agents

When you send a message in the builder, Koda routes it to one or both of these agents depending on the mode you choose in Environment.

• The Supervisor acts like a product lead. It understands your goal, follows the App Roadmap, breaks work into assignments, reviews what the Xcode agent returns, updates plan statuses, and asks clarifying questions when something is unclear.
• The Xcode agent acts like an iOS engineer. It edits the project, builds, runs the app in the simulator or on a device, and fixes compile or runtime problems until the assigned work is done.
• In chat you will often see separate Supervisor and Xcode sections as planning, implementation, and review unfold.

How they work together

• Supervisor + Xcode (default): your message goes to the Supervisor. It interprets the request against the App Roadmap, breaks the work into concrete technical items for the Xcode agent, delegates those items one at a time, and reviews each result before accepting it, updating plan status, or continuing.
• Xcode Agent Only: your message goes straight to the Xcode agent. There is no Supervisor breakdown, delegation, or review loop. Use this when you want a direct change and do not need roadmap orchestration.
• Choose the mode in Environment before a longer build request so the right agent owns the conversation.

App Roadmap and Current Work Plan

Koda keeps two related plans. They look similar in the UI, but they serve different scopes.

• The App Roadmap is the project-level build plan. It persists across chats and lists the major steps for the app. The Supervisor treats it as the queue of product work—usually one roadmap step at a time—and updates each item’s status as work moves from Pending through In progress, Awaiting review, and Done.
• You can reshape that queue anytime with Edit on the App Roadmap (reorder, rename, mark complete, add or remove steps). Details are in Develop your app.
• The Current Work Plan is a short, read-only checklist for the current chat. It appears when the agents break a request into tactical sub-steps—for example fixing a crash, exploring a screen, or implementing one slice of a larger roadmap item.
• Finishing a Current Work Plan can advance the parent App Roadmap step. Completing the roadmap is the long-term measure of product progress; the Current Work Plan is only for the conversation in front of you.

Example prompts

These are the kinds of requests that move an app forward. They describe outcomes in everyday product language—no engineering jargon required.

• “Add a welcome screen with a Continue button, and remember when someone has finished onboarding so we don’t show it again.”
• “Build the first version of a workout tracker: a tab bar with Today, History, and Profile. Today should list the day’s exercises with checkboxes.”
• “Focus on the next App Roadmap step for sign-in: email login and a simple profile screen using our Supabase connection.”
• “The app crashes when I tap Save on Settings. Fix that before moving on to the next roadmap item.”
• “Make the home screen feel more premium: soft blue background, rounded buttons, and a clear headline that explains what the app does.”
• “Add a Shop tab where customers can browse our Shopify catalog, add items to a cart, and check out.”