Modes

Macaly has three modes that control how the agent approaches your requests. Each mode changes when the agent creates plans and asks questions, giving you different levels of speed versus visibility. You can switch between modes anytime using the mode selector in the chat interface, right next to where you type your message. The mode you choose depends on what you’re building and how much control you want over the process.

​

Auto (default)

Auto mode lets the agent decide when to plan and when to build directly. For simple requests, the agent builds right away. For complex or unclear requests, it creates a plan first or asks clarifying questions. This is the default mode because it balances speed and visibility. You get fast results when appropriate, and the agent slows down to check with you when needed. Use Auto when:

• You’re working on a mix of simple and complex tasks
• You want the agent to make judgment calls
• You’re not sure which mode fits your request

​

Plan

Plan mode means the agent always creates a plan before building anything. Turn it on from the mode selector next to the message box. The agent breaks your request into steps, asks any clarifying questions, shows you the approach, and waits for your approval. No code is written until you review and confirm the plan. This gives you full visibility into what will happen before it happens. You can see the agent’s interpretation of your request and adjust the approach before work starts. Use Plan when:

• You’re building a complex feature
• You want to understand what will be built
• You want to review the approach before committing
• You’re learning how Macaly works

​

Build

Build mode means the agent works without interruption. It doesn’t create plans or ask questions. It builds directly based on your request, making reasonable assumptions when details are unclear. Use Build when:

• You know exactly what you want
• You’re making simple, straightforward changes
• You’re continuing work from an approved plan
• You don’t want to wait for questions or plans

​

What each mode can do

Not all modes let the agent pause for your input.

​

Why planning helps

Planning isn’t just about control. The agent often builds better when it thinks through the approach first. Catch misunderstandings early
If the plan doesn’t match what you had in mind, you can correct it immediately. Fixing a plan is easier than undoing finished work. See what will change
Plans explain the approach in plain language. You don’t need technical knowledge to understand what will happen. Adjust direction before work starts
You can give feedback on the plan to change the approach, add details, or remove parts you don’t need. Complex features benefit most
When adding multi-page features, authentication, or database functionality, a plan ensures alignment before significant work begins.

​

When planning isn’t necessary

For simple requests, planning adds overhead without value:

• Changing text or content
• Adjusting colors and styles
• Fixing obvious bugs
• Anything that takes fewer than three steps

For these, Auto, Build, or Visual edits gets you results faster.

​

Frequently asked questions