AI coding app quick start

Zcode quick start

Connect Guard to Zcode so every tool call and config change is checked before it runs.

Install GuardBack to install

Prerequisite

Install Guard

If you haven't installed Guard yet, run the install script first. This installs hol-guard via pipx and configures it for Zcode in one step.

Install Guard for Zcode
Preparing install command…

Already have Guard installed? Skip to the harness command below. Full install guide.

Coverage

Event surfaces

shellpromptmcp_toolfile_read

Native approval

No

Browser fallback

Yes

Resume support

No

Smoke command

hol-guard install zcode --dry-run

Known blind spot

Inline edits applied directly by the model without a tool call are not visible to Guard, and background sessions that run without an active terminal do not surface hook events.

Harness command

Attach to Zcode

Terminal

hol-guard install zcode

Guard stays local by default — no account required to protect your first session. Connect Guard Cloud later to sync security records across your devices.

What Guard checks

  • ~/.zcode/cli/config.json and ~/.zcode/cli/plugins/
  • declared MCP server entries and tool surfaces
  • command surfaces and plugin declarations

What install changes

  • Installs Guard in wrapper mode so you can protect Zcode without changing your existing setup.
  • Keeps a local security record for every approval and block so your team can reuse past decisions.

Verification

Confirm the setup before your first protected session.

1

Run the setup command

Start with the Guard command matched to this AI coding app and its setup mode.

Command

hol-guard install zcode
2

Run the next verification commands

Confirm Guard sees the expected config paths before your first protected session.

Command

hol-guard doctor zcode
hol-guard run zcode --dry-run
3

Check your first security record

After Guard records a local decision, open the receipt list to confirm what was scanned.

Command

hol-guard receipts

Safe demo & test protection

Use --dry-run for demos and CI. Guard scans and reports without blocking, so you can show what it catches without interrupting a live session.

Sync to Guard Cloud

Connect Guard Cloud to carry your security records, team memory, and approval history across every machine and teammate — no rebuilding approvals when you switch devices.

Review Guard Cloud plans →

Troubleshooting

Something not working?

  • Guard does not intercept launches

    Run hol-guard doctor zcode and check that the wrapper path matches your installed binary.

  • No security record after the first run

    Check that ~/.hol-guard/ is writable. Guard writes every decision there by default.

  • Cloud sync not reflecting local decisions

    Run hol-guard sync --status to see if Guard Cloud can reach the server. Local protection keeps running even when sync is unavailable.

Approval surface

Guard local approval center (browser, localhost) via wrapper mode — opens when a new or changed tool call or config entry needs a decision.

Run command

hol-guard run zcode

Uninstall / revert

Guard leaves no background services. Your approval history stays on disk in ~/.hol-guard/ unless you delete that folder.

Uninstall command

hol-guard uninstall zcode

Current phase notes

  • Inline edits applied directly by the model without a tool call are not visible to Guard, and background sessions that run without an active terminal do not surface hook events.
  • Zcode native approval surface is not replaced — Guard intercepts at the wrapper layer.

Zcode FAQ

Does HOL Guard replace Zcode permissions?
No. It adds a local review layer around risky actions so permissions are easier to understand.
Does HOL Guard publish my activity?
No. Public warnings are opt-in, redacted, and held for moderation before indexing.

Related security content