Desktop & extensions · Verify

Local Client Runtime Security Check

Verify one browser-extension or desktop-app local runtime security invariant through bounded permission, storage, messaging/IPC, update/restart, and failure scenarios.

Vibe Coding 1.3.0 · vibe-desktop · English technical instructions

← Back to search

Use this workflow

Use this workflow in Codex or Claude Code with the free Vibe Coding plugin. Choose your assistant and prompt language, then add your task details after the prompt.

Prompt

Use $vibe-desktop, workflow “Local Client Runtime Security Check” (ID: local-client-runtime-security-check). Follow this workflow for the task below. Report the result in English.

Install the plugin

Operation

Verify the selected invariant through bounded scenarios in an authorized environment. Do not turn verification into unrelated implementation. Return passed, failed or blocked, with actual evidence and any missing required scenario.

Goal

Verify one browser-extension or desktop-app local runtime security invariant through bounded permission, storage, messaging/IPC, update/restart, and failure scenarios.

Required input

Provide selected local-runtime boundary, expected security behavior, implementation summary or patch boundary, supported platform/browser, safe environment, fixtures/accounts, and commands/manual scenarios.

Scenarios

Verify permission request/denial/revocation behavior.
Verify message/IPC payload validation and trust-boundary rejection.
Verify token/secret/local data storage and logging behavior.
Exercise reload/restart/update/offline/failure states relevant to the selected boundary.
Run build/package checks when the patch changes release artifacts.

Workflow ID: local-client-runtime-security-check · View the versioned source · Shared workflow and authority rules