Turn an idea into work you can review and use.

ACE is for creators building their first app, founders testing an idea, and developers who want help implementing and reviewing software. You give the work a goal, provide useful context and decide what a successful result looks like.

You can start with a conversation, give a single agent a focused assignment, or coordinate a team with different roles. Projects keep the conversations, files, tasks and review history together.

The latest ACE Dev also brings email drafts and documents onto the same Tasks board. Each task has a clear finish line, from an accepted document to a confirmed GitHub merge.

1. Get the macOS or Windows installer from the download page, install ACE and open it.
2. Sign in with your ACE account and complete any access steps shown in the app.
3. Open Settings > Connected Tools. Follow the setup guide for the AI provider you want to use. It checks the required tool and account connection.
4. Return to Home and choose an available model in the Assistant composer. Check the account and funding source shown with it.
5. Describe a new project, open a saved project, or use New project for guided setup.

Start with one small result you can inspect. For an existing app, try: “Add a search field to the customer list. Match names, show a useful empty state, and check it at a narrow window width.”

1. Open the project and choose Tasks > New task. Write the assignment and say how you will check it.
2. Choose the project team or an enabled agent. Use the planning, implementation and review workflow when you want help through each stage. Check the timing and automatic progression before creating it.
3. Open the card to follow activity, read the plan and inspect recorded checks. If it waits in Inbox, use Start. Answer any request for information or approval.
4. For coding work, open its Build conversation and Changes. Inspect the diff and run the app preview where available. Ask for changes if the result misses your brief.
5. Review the final outcome. Use Apply changes when you want to integrate reviewed work locally, or the GitHub delivery action when you intend to merge. Confirm the destination and read the resulting status.

Home combines Ace Assistant with your saved projects. Choose New Project or an existing project beside the composer, choose a connected model, and describe the work in your own words.

For example: “Set up a team to build a simple booking app. Have one agent plan it and another review the implementation.” Ace can propose the team, model choices, workflow connections and run limits.

Open Review team, models and limits to inspect the proposal. Tell Ace what to change, then use the confirmation tick when the setup is right. Confirmation applies the saved plan and opens its canvas. A saved setup, a started run and a saved schedule each have their own status.

The microphone turns speech into an editable draft. Check the text before sending. You can reopen Ace Assistant inside a project to inspect or adjust its setup.

A project holds your team, conversations, Tasks board and files. Use guided setup to start a new project, open an existing local repository, or choose a repository from your connected GitHub account.

Tasks, Ideate and Build are three views of the same project. Build conversations have their own execution workspace and branch, so you can inspect an assignment’s changes before applying them to the source project.

Your source files remain in normal local Git repositories. Opening another conversation or seeing a task reach Review does not automatically merge its branch into your project.

Use Tasks to see what is waiting, running, ready for review and finished. Open any card for its assignment, worker, activity, notes and evidence. Search, labels and Needs attention help you find the work that needs a decision.

In ACE Dev, New task proposes the type, destination and final step from your prompt. Adjust them before starting, or set defaults for each type. You can change an inactive task’s stage, but moving a card to Done is not a substitute for reaching its finish line.

Pause prevents future automatic stages while an active run finishes. Use Stop run to stop active work. Close without verification records a closure; it does not certify a successful result.

Use Ideate to explore a problem, compare options and agree on a brief with your agents. The canvas shows the team and its workflow; the chat keeps the conversation together. Switch between full chat and the canvas with the layout control.

Give the team references, constraints and a definition of done. For a booking app, that might include who can book, what happens when a slot is full, and how you will check the result.

Open a message’s thread to follow its work or reply without losing your place in the main conversation. The Activity panel shows actual project activity. Generated images can appear in the completed answer and Generated Assets.

Team memory keeps useful shared notes for the board. Open it to confirm, correct or forget a note, or change how new notes are saved. Automatically saved notes are labelled unverified.

When the brief is ready, choose Send to Build on the message. Review the assignment and agent before sending. The linked Build chat keeps the source context, and its results can return to Ideate for review and follow-up.

Each Build chat has one assigned agent and its own coding workspace. Choose New chat, write the assignment, then choose Start now or Add to queue. You can also arrive here from a Tasks card or an Ideate handoff.

1. Follow the conversation and open its work details when you need to inspect commands, files or an interruption.
2. Open Changes to inspect the file list, diff, review state and next action. Use Preview to inspect the running app when available.
3. Request review or continue the chat with a correction. A review of an earlier run does not approve later changes.
4. Use the offered local integration or GitHub merge action after the required checks pass. Verify the named repository and branch before delivery.

Conflicts, failed checks and requested changes keep work in Review with an explanation. A GitHub delivery is complete when ACE records the confirmed merge. Locally applied changes and a passed review have their own outcomes.

The Ideate canvas lets you configure agent roles, model choices, reference documents and connections between workflow steps. Start with a clear lead and add a reviewer or specialist when the assignment needs one.

Document nodes add reference material. Connections describe how agents collaborate, review or hand work to one another. Configure loops and review conditions for work that needs several passes, then inspect the actual result and recorded checks.

Smart Actions connects a settled Ideate brief to Build. Manual, Assisted and Autopilot settings control handoff and follow-up behavior. Review the settings before enabling automatic transitions; automatic merge is a separate choice with its own destination and verification requirements.

A useful brief names the output, the boundaries, the checks and the final action. For example: “Build the booking form, verify the full-slot error, and leave the reviewed changes ready for me to apply.”

Open Settings > Connected Tools to install, connect or repair a provider. Use the ready models shown in the picker; availability depends on the provider, account and execution route.

Claude, Codex and Gemini have different setup and execution requirements. Additional providers appear where supported. A successful account login does not make every model or provider route executable; follow the readiness message in ACE.

Gemini uses Gemini CLI for supported API, Code Assist Standard and Enterprise, and Google Cloud connections, with OpenRouter where configured. Antigravity task execution remains unavailable because its CLI does not yet support safe per-run discovery isolation. Signing in alone does not enable it.

The Assistant has its own model selector. Project agents have their own model and role configuration. Check both when you change providers or accounts.

Open the library from Agent Config to browse Skills, Plugins and Bundles. Skills supply instructions for a kind of work. Plugins connect tools and services. Bundles collect related skills and plugin connections.

1. Choose a skill or review an imported bundle before installing it.
2. Complete the connection steps for any plugin you need.
3. Enable the relevant components for the agent in Agent Config.
4. Give the agent an assignment that explains how the capability should be used, and inspect its result.

Installing a bundle does not finish its service connections or automatically enable every component for every agent. External services keep their own access requirements.

In New task, choose Once, now, a schedule, or the next verified completion of another task in the project. Check the timezone and next occurrence before saving. Task schedules run while ACE is open and skip occurrences missed while it is closed.

Automatic progression moves an eligible task through its configured stages. Project and task pause controls stop future stages; running work can finish. The project’s capacity setting limits simultaneous Build agents. A scheduled task waits while its previous run still needs resolution.

You can also ask Ace Assistant to schedule a team workflow. Review the saved schedule and its execution device. Assistant settings shows whether this desktop installation supports background runs. Background schedules still need an awake, online, signed-in device; follow the displayed execution status.

From the Inbox column menu, connect Gmail, search for a message, inspect its preview and import it as a task. Importing one email saves it to Inbox without starting an agent. The task retains the source account and message details; attachments are excluded.

In ACE Dev, you can separately enable automatic investigation of clear bug reports. Uncertain reports wait in Inbox. Delivery defaults to keeping the verified fix for review; opening or merging a pull request requires an explicit destination and delivery choice.

In ACE Dev, email tasks can prepare replies for review. If Gmail does not confirm a send or save, the task shows Check Gmail. Check the mailbox before marking it complete or trying again, so an uncertain delivery does not become a duplicate.

Software health looks at the project’s GitHub issues, checks and recorded verification. Sponsor enquiries looks at Gmail threads matching your search. Saving a responsibility does not scan anything; choose Scan now or explicitly enable Watch automatically.

Read each suggestion’s evidence, proposed action and completion criteria. Choose Add to Inbox, Later or Dismiss. Accepting a suggestion creates a task for you to start; it does not begin execution. Suggested tasks retain a review step for their final action.

Automatic watching runs while ACE is open and respects project pause. Use Pause watching to stop future scans or Cancel scan to stop the active one. A scan can finish without finding worthwhile work.

Open a pending request to read the action and its context before approving or denying it. Closing the notification does not settle the task’s decision. Review settings, workflow verification and the task’s final action continue to determine what happens next.

Projects, generated files and workspaces live on your computer. Cloud model runs send prompts and selected context to the connected provider. Plugins and delivery actions can send information to their connected services.

Keep credentials out of prompts and project files. Review provider and plugin access before including sensitive material, and inspect changes before applying or delivering them.

In ACE Dev, Settings > Feedback > Send error reports automatically controls automatic diagnostic reports. Review that setting when choosing what information to share with support.

Open Settings > Updates to check content updates and desktop updates. Earlier Settings layouts call this area Control Plane. Read the update status and let active work finish before restarting when prompted.

Updating this website does not update your installed app. Check your app’s release channel and update status if a documented control is missing.

Start with the message on the affected task, connection or update. It tells you which part needs attention and often offers a recovery action.

If the issue continues, use Settings > Feedback. Include the action you took, what you expected, the visible error and whether you use ACE or ACE Dev. Remove credentials and unrelated private content from any details you provide.

ACE is a desktop application with a local runtime. The desktop shell handles native integration and updates. The runtime serves the interface, manages workspaces, runs connected model tools and records task activity and verification.

Git-backed workspaces isolate coding assignments. Live events keep conversations and task status updated. Connected providers perform model execution, while plugins supply additional tools. Hosted account and access services handle sign-in and ACE access separately.

Development and production runtime releases are separate from deployment of the hosted website. Your installed app receives updates from its own release channel.