crisp-tui command protection

Reviews crisp-tui shell commands that change a Crisp support inbox. `crisp-tui ctl draft` writes a reply or internal note into the composer of the running TUI and never sends it. `crisp-tui cli` forwards every remaining argument to crispctl, whose reply, assign, segment, resolve, and reopen commands write immediately. Read-only control commands (ctl state, goto, screen, details, conversations, messages, drafts, read, and refresh) are not matched. ctl state is an inbox snapshot, not a resolve. The Unix-socket control protocol is not a shell command and is outside this extension. Pinned to crisp-tui 0.2.0 (ca38f362ea558cb09a82fbf3ef1aba3e6fb8692c). The listing declares 2 rules and 2 permission checks. 2 operations · 2 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @linyiru, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

2 operations · 2 reviewed by default. Examples: crisp-tui cli reply session_1 --text 'Hello!' --profile sandbox --json (reviewed by default); crisp-tui ctl draft session_1 "Let me check that for you." (reviewed by default). These are catalog defaults, not your workspace policy.

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.crisp-tui in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 2 rules and 2 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.