Secret details
Open a stored secret from Secrets to inspect its contents, access settings, and creation and update times. Edit secret changes its name and description in the Secret editor. Contents are managed separately below.
Environment variables
Section titled “Environment variables”An environment secret lists each variable by its stored name. Sensitive values are hidden and marked Sensitive; non-sensitive values are displayed automatically.
| Action | Behavior |
|---|---|
| Show / Hide | Reveal or conceal one sensitive value. Revealing does not change its sensitivity or client access settings. |
| Copy | Copy the complete value to the clipboard without changing the stored value or requiring it to remain visible. |
| Edit | Open the Environment variable editor for its name, value, and sensitivity. |
| Add | Create another variable in this secret. |
Revealing, copying, or opening an available sensitive value for editing uses your configured device authentication. A current authentication session can satisfy the check. Non-sensitive values do not require this protected-value check.
Revealed values are hidden again when you select another secret or upload, leave Secrets, or put the app in the background. Sensitive values copied with Copy are marked sensitive for Android. Android controls how long copied items remain on the clipboard.
Unavailable values
Section titled “Unavailable values”If an encryption key is unavailable on this phone, the variable’s name remains visible but its value cannot be shown or copied. Open Edit to supply a replacement. Agentknock also reports values it cannot decrypt or verify; it does not substitute an empty value for failed reads.
SSH key
Section titled “SSH key”An SSH secret shows its algorithm, bit length, public-key comment, and OpenSSH fingerprint. Copy public key copies the complete public-key line. Expand Details to see that line and open Replace key.
The comment’s edit action changes only the public label. It does not change the key material or fingerprint. The comment is optional, must fit on one line, and has surrounding whitespace removed when saved.
Replace SSH key generates or imports replacement key material. Register its public key with the services that should accept it. Replacing a key does not revoke the old public key at those services.
The private key is stored encrypted and used on the phone for SSH authentication and Git signing. This screen offers no private-key reveal, copy, or export action. Private key unavailable means the public identity is still known, but the phone cannot use the stored private key. Replace it with an available key to restore those operations.
Client access
Section titled “Client access”Access settings control release of sensitive environment values, or SSH authentication and Git signing. They do not require approval for non-sensitive values or public SSH keys. Paired clients can also list secret names, descriptions, types, and environment variable names regardless of these settings.
Approval modes
Section titled “Approval modes”Default for all clients applies to every client without an override. New secrets start with Ask.
| Setting | Behavior |
|---|---|
| Deny | Automatically deny protected uses of this secret. |
| Ask | Leave protected uses for you to allow or deny on the phone. |
| AI | Ask the AI reviewer to allow, deny, or leave the decision to you using your instructions and the request context. Requires active AI review access. |
| Allow | Automatically allow protected uses without manual or AI review. |
For environment secrets, approval depends on the variables actually requested. A command requesting only non-sensitive values needs no approval, even when the secret’s setting is Deny. For SSH secrets, obtaining the public key and starting a command does not approve its later authentication or signing operations; those uses are evaluated separately.
When a command requests several secrets, a denial for any protected use prevents the request from being allowed. If any required decision is Ask, the initial command request goes directly to you; it does not first run an AI review for other secrets. See Secret use requests for combined requests and decisions.
Selecting AI without active access opens information about paid AI review access and a View plans action. An existing AI setting is retained while access is inactive, with requests asking you instead; it resumes when AI review becomes active. If access cannot be checked or a review fails, manual decisions remain available. See Plan and billing.
Per-client overrides
Section titled “Per-client overrides”Each client has its own row. Uses default and a muted selection mean it follows the secret’s default mode, including later changes to that default.
Selecting a mode in a client row saves an explicit override for that client and secret. Selecting the same mode as the current default still creates an override, so a later default change will not affect that client. Use default removes the override and resumes inheritance. These settings save when selected.
An override does not activate a blocked or removed client. Manage the client’s connection state from Client details.
Temporary access
Section titled “Temporary access”Temporary access is created while allowing a request, lasts four hours, and belongs to one client, secret, and operation:
| Operation shown | Scope |
|---|---|
| Secret values for any command | Subsequent commands from that client can receive this secret’s sensitive values. |
| Git signing for any repository | That client can request Git signatures using this key across repositories. |
| SSH authentication for any server | That client can authenticate using this key across servers. |
These grants skip manual and AI review for their operation. They do not extend to the other operation types. Deny still blocks protected access.
Each grant shows its client, operation, and expiry. End removes that grant immediately, so the saved approval settings apply to subsequent uses. A blocked client pauses use of a grant without extending its expiry; reactivating the client can make the remaining time usable again. Using a grant does not restart its four-hour period.
Changes that end temporary access
Section titled “Changes that end temporary access”Renaming the secret, changing its AI instructions, adding, editing, or deleting a variable, replacing its SSH key, or approving an update or replacement upload ends that secret’s temporary grants.
Changing the default approval mode ends grants for clients using that default. Changing a client’s effective approval mode ends that client’s grants for this secret. Switching between an explicit mode and an identical inherited mode preserves them. Description-only changes and public-key-comment edits also preserve grants.
Changes to global or client AI instructions preserve existing grants. To require a new decision under those instructions, end the relevant grants explicitly. Grants survive an ordinary app restart, but are cleared when app data is restored to an installation. Ending access cannot retrieve values already delivered to a command or undo an authentication or signature already completed.
Secret AI instructions
Section titled “Secret AI instructions”Secret AI instructions provides guidance for AI decisions about this secret. Describe its intended use and the circumstances in which it may or may not be used. These instructions are combined with global instructions and the requesting client’s instructions when this secret is subject to AI review.
Instructions do not change the selected access mode or restrict Allow and temporary access. They can be edited while AI review is inactive and will be used when it becomes active. Do not include secret values in instructions: their text is sent to the AI reviewer.
Delete a secret
Section titled “Delete a secret”Choose Delete secret from the menu and confirm to remove the secret, its stored contents, client overrides, and temporary grants. This is permanent within Agentknock. It does not revoke a token at its issuing service or remove an SSH public key from servers and accounts where you registered it.