> For the complete documentation index, see [llms.txt](https://docs.nerve-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerve-protocol.com/guides/jack-in-guide.md). # Jack-In Guide This guide walks through activating your first Nerve Protocol mission — from key generation and Console installation through launching an autonomous agent workflow and reviewing its zero-knowledge compliance receipt. *** ## 1. Generate and Register Access Keys Nerve Protocol uses hardware-backed keys for session authentication. Software keys are not supported. * Generate keys using a YubiKey, Ledger hardware wallet, or a TPM-backed device that supports TEE attestation. * Register the public key portion during the Nerve onboarding flow. The private key never leaves your hardware device. * Store your recovery material (seed phrase or key backup) offline, on air-gapped media. A lost key cannot be recovered by Nerve — there is no server-side key escrow. *** ## 2. Install the Nerve Console 1. Download the Console launcher for your operating system from the official release page. 2. Verify the binary against the published attestation hash before running. Do not skip this step — it confirms the binary has not been tampered with. 3. Run the installer. It provisions a local enclave container; no elevated (root/admin) system access is required. 4. Execute `nerve jackin` to run the initial attestation check. The Console validates the local enclave against the remote attestation service and will not proceed if the check fails. *** ## 3. Authenticate and Enter the Network * On first launch, you will receive a **Jack-In Phrase** — a one-time authentication challenge processed by the Enclave Integrity Monitor handling session bootstrapping. * The Monitor validates your voiceprint against your registered biometric credential and, on success, provisions the operator session deck. * Optional: enable presence masking to make your session invisible to collaborators until you initiate an explicit disclosure handshake. *** ## 4. Connect Your Stack Before launching missions, wire the external systems your agents will need to access. Refer to the [Integration Matrix](/guides/integration-matrix.md) for platform-specific setup steps. Quick reference: * **Uber and Amazon:** Complete OAuth via the encrypted in-enclave browser. Tokens are sealed to the enclave on authorization; they never touch the host browser or OS. * **Slack and Notion:** Install the Nerve app from each platform's marketplace. Scopes default to read-only until explicitly elevated for a specific mission. * **Google Workspace:** Configure domain-wide delegation using a restricted service account. Attested access tokens are issued per mission and expire at session close. Each integration you add receives a policy capsule defining its allowed data scope, retention window, and expiration. Review these before proceeding — agents cannot access data outside a capsule's declared boundaries. *** ## 5. Launch Your First Mission 1. Open the **Mission Deck** from the Console navigation. 2. Open the command palette with `CTRL + REDPILL`. 3. Enter a natural language intent, for example: > "Prepare the investor update, schedule a board call for next Thursday, and keep all documents sealed inside the enclave." 4. The Console compiles the intent into a deterministic mission graph and presents it for review. Inspect the graph — it shows exactly which agents will run, which integrations they will access, and what policy capsules apply to each step. 5. Approve the graph. Agents begin executing in the Executor Bay. *** ## 6. Review and Share Results * Open the **Signal Lattice** view to review compiled insights and agent-recommended actions. * Generate a zero-knowledge receipt from the Audit Trail panel to produce cryptographic proof of mission completion. The receipt can be shared with stakeholders, regulators, or auditors — it proves what happened without revealing mission content. * To share a redacted summary, use the selective disclosure export. Choose which fields to surface; the remainder stays sealed. *** ## 7. Close the Session * Enter `JACKOUT` in the Console or close the application window. * The enclave is wiped, session state is destroyed, and the capsule dissolves. * If you want to reuse this mission configuration, export an encrypted mission template before closing. Templates are stored encrypted under your key and can be re-launched without re-authorizing each integration. *** ## Troubleshooting **Attestation failure on startup.** Verify that your hardware firmware is up to date and that the attestation service endpoint is reachable through your network. If operating behind a corporate proxy, ensure the attestation relay is configured in your Console settings. **Integration timeout or authorization error.** Reconfirm that the OAuth scopes granted to the Nerve app match the policy capsule declared for the integration. Mismatched scopes cause automatic connector suspension. **Agent stalls or does not proceed.** An Enclave Integrity Monitor may have throttled or quarantined the agent due to a policy capsule violation or a failed mid-mission attestation check. Open the Integrity Monitor dashboard from the Executor Bay to view the specific compliance score, the failing policy rule, and recommended remediation steps. *** For advanced agent configuration, dedicated enclave cluster setup, and SDK-based custom module development, see the [TEE Nodes](/architecture/tee-nodes.md) reference. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nerve-protocol.com/guides/jack-in-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.