Quick start

You need an Apple silicon Mac for the desktop preview and a model connection. Choose a small local project without sensitive files for your first task.

Set up the app

Install Wuu and open the copy in /Applications. Release builds are signed with an Apple Developer ID and notarized. If you use an older ad-hoc preview, macOS may block the first launch; the installation guide explains how to open it.
Choose your optional plugins in the first-run setup. The recommended selection is TODO and Automation; you can change it later in the plugin settings.
Select an agent engine. Wuu is built in; Codex and Claude Code depend on a working local CLI installation.
For the Wuu engine, configure a model service or reuse a supported local subscription login.
Optionally import website cookies from a local browser. Recently active profiles appear first; click Import cookies for the profile you want, or Skip for now. You can also import later in Settings → Browser.
Select recent projects discovered from local Codex and Claude Code history, or choose a folder. Import the selected workspaces to start there, or skip and add them later. Only workspace directories are added; conversation histories and project files stay in place.

Cookie import currently supports Chrome, Chromium, Doubao, Edge, Brave, Vivaldi, and Opera on macOS. Discovery reads profile metadata, not cookie values or passwords. Recent activity helps order the list; it does not measure how often you use a browser. Import may request macOS Keychain access. Imported cookies are shared by Wuu’s browser tabs, allowing the agent to use signed-in sites; some sites still require signing in again. Safari and Firefox are not supported.

You can also change model connections later in Settings → Model providers. Check the model shown in the composer before sending: the conversation’s selection can differ from the saved defaults.

Read, change, and check

Select Read only in the permission menu and ask:

Read this project without changing any files. Explain what it does and how to run its tests.

Once you recognize the project and its test commands, switch to Standard for a small edit. Describe the result you want and ask the agent to run the relevant checks. The first-task guide walks through this step.

Open /diff to review Git changes and read the command results before accepting the work. A reply saying “done” does not establish that a test passed. Continue in the same conversation for corrections or follow-up work.

Prompts, relevant file contents, and tool results can be sent to the selected model service. Read permissions and the security model before using private projects.

Use the CLI

The desktop does not require a separate CLI. To work from a terminal, install it, configure a provider, and run this from your project folder:

wuu exec --permission-mode read_only "read this project and explain how to run its tests"

See wuu exec for script input, saved sessions, and machine-readable output. If setup fails, use troubleshooting.