Contextual tools & permissions

Add supported tools and selected context to a conversation. Your model remains an independent choice.

Chat

Use the selected model for technical questions and supported source context. Files are selected explicitly. Action-specific approval appears only when the runtime proposes an actual governed tool action.

Code

Inspect explicitly selected UTF-8 source files, request patch artifacts and approve bounded Node tests. Hosted checks run inside an isolated network-disabled container. A generated patch does not modify your local file: CLI and editor clients require a separate local diff review and confirmation.

Pentest

Bounded HTTP checks require a confirmed operator, authorized origins, exclusions and an active time window of at most 24 hours. The current gateway permits one GET or HEAD request, no redirects and no concurrent requests. Production targets must resolve to public IP addresses. Runtime availability is checked before tool selection; no arbitrary scanner, shell or private-network access is promised.

Reverse

Explicitly selected PE, ELF and .NET artifacts are quarantined for bounded static inspection in an isolated runner. Uploaded binaries are not executed. Static observations are not a maliciousness or exploitability verdict.

Availability and approval

Installed clients do not bypass account admission, model access, usage limits or runtime readiness. Unavailable tool runners cannot execute work. Approve only the actual tool, exact arguments, selected scope and limits shown for the proposed action.