ZCode Core Capability Settings
Step 1 · Install and Sign In has ZCode installed and signed in → this guide turns on its core capabilities so it can go from “chatting” to “doing”.
🌟 Goal: turn on Full Access + Computer Control + Browser Control + memory and indexing, understand the authorization mechanisms and operational purposes, so ZCode can actually operate your computer and projects. Plan and model selection are grouped in Step 3 and are not touched here. It usually takes 5–10 minutes.
Follow This Checklist
- Enable Full Access;
- Enable Computer Control and its prompt-box button;
- Enable Built-in Browser Control;
- Enable workspace memory;
- Enable indexing for new folders and repositories.
1. Enable Full Access
Create a new task, open the permission menu at the lower left of the prompt box, and select Full Access.
This prevents ZCode from pausing repeatedly for permission prompts while editing files, running commands, or using tools, making it much easier to complete workflows continuously.
How to tell this step is correct: the permission label at the lower left of the prompt box clearly displays "Full Access". While the screenshot also highlights the model menu, in this step select only Full Access; models are configured in Step 3.
Why the Beginner Tutorial Recommends Full Access
Many newcomers feel hesitant when seeing "Full Access": does this pose a security risk? Will the AI delete files by mistake?
Here is the operational rationale and why you can proceed with confidence:
- Scoped to trusted workspace directories: ZCode does not roam freely across your entire disk. Its file reading, writing, and command executions are strictly confined by default to the local project folder opened for the active task.
- Critical checkpoints retain manual reviews: Across the entire guided workflow, vital delivery actions and production releases retain manual confirmation checkpoints. The AI acts as an assistant preparing drafts and code modifications, while final control remains in your hands.
- Downgrade to per-action prompts anytime: If you ever feel uneasy about a sensitive task, you can switch the permission mode back to default manual approval. However, the downside is significant: the AI will halt and prompt for a confirmation click on every single file read and command run, interrupting a simple workflow dozens of times.
- Everyday recommendation: When building websites, organizing business data, and testing scripts in your trusted directory, Full Access provides the smoothest and most efficient experience.
2. Enable Computer Control
Open Settings → Computer Control, then:
- Turn on Enable Computer Control;
- Turn on Show the computer-action button in the prompt box;
- Confirm that Accessibility shows authorized;
- Confirm that Screen Recording shows authorized.
How to tell this step is correct: both toggle switches in the Computer Control settings page are highlighted on, and green "Authorized" labels appear below for Accessibility and Screen Recording.
Return to the new-task screen and confirm that the computer-action button appears near the prompt box.
What Happens If You Do Not Enable Computer Control
Beginners often ask: why not just have the AI read and write text? Why does it need computer control?
- Direct consequences of disabling it: When you hit an unexpected error modal while running a local site, the AI cannot see the actual visual error dialog on your screen. It cannot click buttons or find configuration switches in graphical interfaces for you, forcing you to manually transcribe error messages or paste screenshots every time.
- Core value of enabling it: It equips the AI with eyes to see your screen and hands to assist with tasks. It can inspect UI errors directly and, with your permission, click interface options and assist with interactive debugging.
Troubleshooting OS Permission Failures
On macOS, strict system-level privacy protections can prevent permission popups from appearing or cause permissions to show as unauthorized even after toggling them on:
- Remedy 1: Manually add permissions if popups do not appear. Open macOS System Settings > Privacy & Security, locate Accessibility and Screen Recording. Click the add button (
+), manually select ZCode from your Applications folder, and ensure the toggle next to it is enabled. - Remedy 2: Restart the app completely after toggling permissions. macOS requires process reloads to recognize permission changes. Simply closing the app window may leave it running in the background; you must completely quit ZCode (
Cmd + Q) and reopen it for the settings page to show "Authorized". - Remedy 3: Check Windows background security shields. On Windows, if control actions fail, verify whether third-party security software is silently blocking screen capture or simulated keystrokes, and add ZCode to the trusted whitelist.
3. Enable Browser Control
Open Settings → Browser Control, then turn on Built-in Browser Control.
Importing your Chrome sign-in state is optional. Use it only when you want ZCode's built-in browser to reuse websites already signed in through Chrome.
How to tell this step is correct: the top toggle switch for Built-in Browser Control is turned on.
What Happens If You Do Not Enable Browser Control
- Direct consequences of disabling it: When analyzing web designs or verifying site layouts, the AI cannot automatically spin up a headless or sandboxed browser to load web pages. It cannot verify whether responsive layouts break or test form submission flows.
- Core value of enabling it: ZCode gains an integrated sandboxed browser environment. It can automatically open pages you just coded, take visual screenshots to check styling, and catch frontend console errors immediately in code, removing the need for manual screen switching and URL pasting.
4. Enable Workspace Memory
Open Memory in the Settings sidebar, then turn on Workspace Memory. If your version has no separate Memory page, look for Workspace Memory under General.
It helps ZCode retain project context, preferences, and confirmed rules within the same workspace, reducing repeated explanations.
How to tell this step is correct: the Workspace Memory toggle is turned on, and the descriptive text below confirms that memory retention is active.
What Difference You Notice Once Enabled
Memory might sound conceptual, but in daily practice the difference is immediately tangible:
- The frustrating experience without memory: Every time you start a new task, the AI acts like a complete stranger. You have to re-explain your background—"we export stainless steel tableware," "our target buyers are European wholesalers," "our primary steel grades are 304 and 316"—every single day.
- The seamless experience with memory: When you start a fresh session days later and ask, "make yesterday's quotation term more accommodating," the AI pulls the historical workspace context automatically without needing you to re-introduce the company or project.
Distinguishing Workspace Memory from Global Memory
Following the clear definitions in the application settings interface:
- Workspace Memory: Retains facts, project rules, and codebase conventions specific to the current project without leaking into unrelated tasks.
- Global Memory: Applies across all projects, preserving your general personal communication preferences (e.g., preferred languages or code formatting style). Beginners only need to turn on Workspace Memory.
5. Enable Repository Indexing
Open Settings → Index Library, then enable:
- Index new folders;
- Index repositories for instant search.
This helps ZCode search files and understand a repository more quickly after opening a new project.
How to tell this step is correct: both toggles on the Index Library settings page remain on, and ZCode automatically builds background semantic and symbol indexes whenever a folder is loaded.
Index Library Mechanics and Practical Impact
Web and automation projects easily span dozens of markdown guides, templates, and script files. Without indexing, every time the AI searches for relevant content, it must scan directories sequentially, resulting in sluggish responses and missed cross-references in nested folders.
With indexing enabled, ZCode continuously indexes file names, symbols, and semantic text in the background:
- Instant file location: When you ask to "find our product specification table," it immediately pinpoints the exact file path;
- Project-wide contextual awareness: When updating a parameter or product link, the AI detects cross-page references upfront, preventing broken links and inconsistencies.
Keeping both indexing toggles on provides the foundation for full project-level visibility.
📋 Settings Pitfalls
| Pitfall | Consequence | How to avoid |
|---|---|---|
| 🔴 Enabling only Full Access, not Computer Control or system permission | File and command permission exists, but the computer-action button will not appear and the screen cannot be controlled | Full Access is a task permission; Computer Control is a separate capability, and Computer Control, Accessibility, and Screen Recording must each be authorized |
| 🟡 Assuming macOS permissions take effect immediately without restarting | The process has not reloaded, causing checks to fail repeatedly | After toggling permissions in System Settings, completely quit ZCode with Cmd + Q and restart it |
| 🟡 Changing the model at this step | You will switch back and forth in Step 3 | Enable capabilities only; choose the model in Step 3 |
| 🟡 Sticking to manual approval out of fear of Full Access | You will be interrupted by dozens of manual confirmation clicks for every simple file operation | Confidently enable Full Access for trusted local projects and rely on manual checkpoints for final deliverables |
| 🟢 Treating “import Chrome sign-in state” as required | An extra step that also involves account data | Import it only when you need Chrome sign-ins in the built-in browser; standard web testing does not require it |
✅ Completion Check
Return to the new-task screen and confirm:
- The permission mode shows Full Access;
- The computer-action button appears in the prompt box;
- System Settings shows Accessibility and Screen Recording as authorized;
- Built-in Browser Control is enabled;
- Workspace Memory is enabled;
- Both indexing switches are enabled.
📚 Further Reading
- 📚 Step 1 · Install and Sign In: go back here if ZCode is not installed yet
- 📚 Step 3 · Plans and Models: choose a built-in plan and a default model
- 📚 Step 4 · Install the ZCode AI Staff Team: have different models work by role
📄 Step 3 · Plans and Models — choose a plan and a default model, and ZCode is ready to start real work.