# VibeLint 4 — Code Security setup VibeLint protects AI-assisted code writes with a fast local gate and a separate deep scan. Free protection keeps working locally when dashboard authorization is unavailable. ## Getting started 1. Open **Dashboard → Get started**, choose your editor and operating system, and copy the generated command. 2. Run that exact command and keep its terminal open. 3. Approve the named device in the browser. The page will show **Browser approved — waiting for this device to finish setup** until the device receives its credential. 4. Wait for **Installation verified; restart your editor**. A download alone is only staged and is not an installation. 5. Fully restart the editor. For Codex, open a new task. 6. Setup is complete only when the real editor session reports **Scanner ready** in the dashboard. The flow is: **dashboard command → browser approval → verified installation → editor restart/new Codex task → scanner ready**. Code Security has no key-based authentication command. `vibelint auth` is a retired compatibility tombstone and never accepts or stores a credential. Agent Control uses separately labelled `vl_agent_…` keys and is unchanged. ## Supported systems and editors Guided setup supports Windows x64, macOS x64/arm64, and Linux x64 with Python 3.10–3.14. The signed native setup application is Windows x64; the guided private-runtime command is available on every listed platform. | Editor | Windows | macOS | Linux | |---|---|---|---| | Codex | `%USERPROFILE%\.codex\config.toml` | `~/.codex/config.toml` | `~/.codex/config.toml` | | Cursor | `%USERPROFILE%\.cursor\mcp.json` | `~/.cursor/mcp.json` | `~/.cursor/mcp.json` | | Claude Code | `%USERPROFILE%\.claude.json` | `~/.claude.json` | `~/.claude.json` | | Antigravity | `%USERPROFILE%\.gemini\config\mcp_config.json` | `~/.gemini/config/mcp_config.json` | `~/.gemini/config/mcp_config.json` | | Devin Desktop | `%USERPROFILE%\.codeium\windsurf\mcp_config.json` | `~/.codeium/windsurf/mcp_config.json` | `~/.codeium/windsurf/mcp_config.json` | `windsurf` is a deprecated one-release alias for Devin Desktop. Claude Code is supported; Claude Desktop is not the same product and is not configured. ## What verified installation guarantees - The account-specific artifact signature and SHA-256 are verified before activation. - Browser authorization is bound to the setup attempt, release, installation, device, and account. - A fresh candidate process refreshes the durable credential and proves the exact Free or Pro detector set. - The Free or Pro gate canary and a cold Semgrep/deep canary pass before activation. - Existing editor configuration is parsed first; unrelated MCP servers are preserved. - The stable launcher is tested after activation. A failed test restores the previous runtime and editor configuration. - Only exact distributions and wrappers proven to be owned by VibeLint can be removed as legacy conflicts. - The dashboard distinguishes local readiness from cloud acknowledgement. It never calls an approved browser or a staged download “connected.” ## Protection and authorization Free gate detectors are secrets, authentication, injection, CORS, and framework misconfiguration; Free deep analysis is Semgrep. Pro additionally enables authorization, rate limiting, prompt injection, LLM output execution, and dependency analysis. If an access token expires and refresh fails, VibeLint immediately keeps the local Free gate active. A later successful refresh warms and verifies Pro separately before promotion. Authorization problems never appear as detector failures. Credentials are stored in Windows Credential Manager, macOS Keychain, or a private Linux directory (`0700`) and file (`0600`). VibeLint does not install an always-on MCP service; each editor owns its MCP process and closing stdin shuts down its worker tree. ## Recovery Run `vibelint doctor --json` for secret-free status. `vibelint doctor --offline` performs no network access or repair. `vibelint doctor --repair` is limited to journal recovery, pending acknowledgement, and allowlisted cleanup. | Status | Meaning | Safe action | |---|---|---| | `staged_not_authorized` | The candidate runtime is staged but browser authorization is unfinished. | Return to the browser approval page, then rerun the same setup command while it remains valid. | | `authorization_exchange_unavailable` | The browser approved this device, but credential exchange is temporarily unavailable. | Leave setup open; it will retry safely while the device code remains valid. | | `credential_revoked` | This device authorization was revoked. | Generate a fresh dashboard setup command and approve this device again. | | `runtime_variant_mismatch` | The staged runtime variant does not match the required account tier. | Generate a fresh setup command so the correct signed runtime variant can be installed. | | `path_runtime_mismatch` | A terminal launcher resolves to a runtime other than the active managed runtime. | Run guided repair so VibeLint can replace only a proven owned launcher with the stable dispatcher. | | `protected_legacy_install` | A proven older VibeLint launcher is in a protected system location. | Keep local protection active and follow the single elevated cleanup action shown by setup. | | `local_ready_cloud_sync_pending` | Local protection is ready while dashboard acknowledgement is pending. | Keep the editor open and retry acknowledgement; local protection remains active. | | `editor_restart_required` | Installation is verified, but the editor has not started a new MCP session. | Fully restart the selected editor and open a new agent task. | | `deep_engine_warming` | The local gate is ready while deep analysis is warming. | Continue using local protection and retry deep status after initialization completes. | | `gate_detector_failed` | The effective local gate detector or worker failed its health check. | Run doctor repair once; if the failure remains, reinstall the signed runtime and report the correlation code. | If a setup command expires or belongs to the wrong account, generate a fresh command from that account’s dashboard. Do not use a generic package command from a project directory because it can resolve an old or source-shadowed installation. ## Local project scans Project scans and pre-commit checks use the same managed entitlement provider. An unmanaged invocation is Free-only. The gate remains the write-protection decision; slower deep results are reported separately. ## Agent Control Agent Control action logging is a separate product surface. Its `vl_agent_…` credentials and `vibelint agent-auth` command are not Code Security setup and are not changed by the browser device flow.