Secret upload request
Open an item under Incoming uploads in Secrets to review data sent by a paired client. The page identifies the client, received time, secret name, type, proposed description when present, and whether the proposal creates, updates, or replaces a secret.
The stored secret stays unchanged until you select Approve. The upload does not inherit automatic approval from the secret’s access settings and is not decided by AI review.
Upload modes
Section titled “Upload modes”| Mode | Effect of approval |
|---|---|
| New secret | Creates a secret using the uploaded contents. Its name must be unused. You can change the proposed name during review. |
| Update | Adds or changes uploaded environment variables and retains variables omitted from the upload. For SSH, installs the uploaded key. |
| Replace | Replaces the existing contents. Environment variables omitted from the upload are removed. For SSH, installs the uploaded key. |
Update and replace require an existing secret with the same name and type. They cannot rename it or change its type. Every environment upload contains at least one variable, and every SSH upload contains a private key.
If a description was supplied, it becomes the saved description, including an explicitly empty description. Update preserves the existing description when none was supplied. New secret and Replace save an empty description when none was supplied.
New secrets start with Ask as their approval mode and no client overrides or AI instructions. Updates and replacements preserve the secret’s access modes, client overrides, and AI instructions, but end its temporary access grants. Approving an upload does not grant the uploading client permission to use sensitive contents.
Environment variables
Section titled “Environment variables”The review groups omitted variables under Not changed or Proposed removals, according to the upload mode. Each uploaded variable shows its name and, for an update or replacement, whether its value is New, Will update, or Unchanged.
These labels compare values with the stored contents at receipt. An Unchanged value can still receive a different sensitivity setting when you approve it. An empty uploaded value sets the variable to an empty string; it does not remove the variable.
Sensitivity and visibility
Section titled “Sensitivity and visibility”Each uploaded variable has a Sensitive switch. Existing variables initially keep their stored sensitivity; new variables start sensitive. Your selections determine the saved sensitivity when the upload is approved.
Sensitive values stay concealed until you use Show. Revealing a value and changing a sensitive value to non-sensitive use your configured device authentication; an existing authenticated session can satisfy the check. Non-sensitive values are shown automatically. Turning sensitivity on hides the value again.
Revealing is optional. You can approve the upload while every sensitive value remains concealed. Approve itself does not require another protected-value authentication check.
Non-sensitive values become available to clients without approval and may be included in AI review context. See Sensitivity before changing this setting.
You cannot edit uploaded variable names or values, omit individual uploaded variables, or change the upload mode on this page. If the proposed contents are wrong, reject the proposal and send a corrected upload.
SSH key
Section titled “SSH key”The SSH review shows the uploaded key’s algorithm, bit length, comment when present, OpenSSH fingerprint, and complete public-key line. It identifies the private key through this public information; the private key itself is not revealed.
For updates and replacements, the page compares the current and proposed fingerprints when key material changes. It distinguishes a comment-only change from a different key and reports when the key material is unchanged.
Replacing a key does not revoke the old public key at external services. Register the proposed public key wherever it should be accepted. See SSH key replacement for effects on existing command sessions.
Approve or reject
Section titled “Approve or reject”For New secret, the name’s edit action changes the name to use on approval. It must be nonblank and unused; surrounding whitespace is removed. The secret naming rules also describe CLI compatibility. This changes only the proposal until you approve it. Updates and replacements always target the uploaded name.
Approve applies the entire proposal. Reject discards it without changing the stored secret. Both decisions remove the pending upload from Secrets. After approval, open the stored secret to inspect or edit the result.
If a create proposal’s chosen name becomes occupied, approval fails and you can choose another name. For an update or replacement, renaming or deleting the target, changing its contents, or changing its secret AI instructions after receipt invalidates the proposal. Agentknock rejects it instead of applying the old review to the changed secret; send a fresh upload.
Approval also fails if uploaded data can no longer be decrypted or verified, or uses unsupported encryption. Agentknock does not partially apply a failed proposal.
Completion and history
Section titled “Completion and history”The CLI completes when the phone has received the proposal; it does not wait for approval or rejection. You can review a received upload after the command has exited, and the proposal remains reviewable if its transfer confirmation later times out. Your eventual decision does not change the CLI’s completed result.
Uploads that are invalid on receipt, such as an update for a missing secret or a mismatched secret type, can be rejected before reaching the incoming list. The CLI reports the rejection. A received upload’s Needs review state is separate from its transfer confirmation.
After a decision, the upload record retains its name, type, change summary, and outcome, but its pending environment values and private-key material are discarded. Approved contents remain in the stored secret. Upload events and outcomes remain available through the audit log within its retention period.
The page distinguishes Approved, Rejected, Ended, and Verification failed outcomes and shows any recorded error. An Approved upload can also report that the client’s final confirmation could not be verified; that warning does not undo the saved secret.
Technical details contains the client software and Agentknock library versions when reported, plus the client ID and request ID.