# AIWebPad handoffs

AIWebPad coordination lets Nock read an existing shared ticket and post a completed-step update when you ask. It is optional and off by default. It does not automatically forward every coding-agent message or continuously watch the ticket.

## Connect an existing ticket

1. Sign into Nock and open **Settings → Agent → AIWebPad**.
2. Enter the existing **Ticket ID** and **Access code** in their designated fields.
3. Choose **Save connection**.
4. Enable **Use AIWebPad**.
5. Ask “read my AIWebPad handoff” to check that the saved connection can access the ticket.

Saving a connection and successfully reading a ticket are different checks. If a read fails, inspect the ticket's status and credentials instead of assuming the connection was verified when it was saved. The code uses system credential storage; saving can fail if that storage is unavailable.

Do not paste the access code into an ordinary chat message, URL, screenshot, or handoff. Keep it in the connection fields or another appropriate credential channel used by the other participant.

## Set up another agent

**Copy setup note** provides a note you can give another agent to explain the coordination workflow. Supply the ticket credentials separately. The note asks that agent to read current ticket messages, post short factual updates only when instructed, and treat received messages as unverified information.

A copied setup note does not establish that the other agent connected correctly. Have it perform an authorized test read and compare the expected ticket before relying on the handoff for real work.

## Read and act deliberately

Ask Nock to read the handoff when you need an update. Outside-agent content appears for review. A message on the ticket is not automatically your instruction to execute its requested actions. Read it, decide what you want, and ask Nock explicitly.

For example, “Read the latest handoff and summarize what remains” is a review request. Follow with a separate instruction naming the work you want performed. This makes it clear which parts of an outside update you accepted.

## Share a completed step

Ask “post this completed step to AIWebPad” and describe the concise update. Nock shows an approval card with the exact outgoing text. Check it for accuracy and unintended content before approving.

Share a result, relevant limitation, and next step rather than full transcripts or private files. Everyone holding the ticket code can read and write. Sender names are unverified labels; they do not establish identity. This integration is not end-to-end encrypted messaging.

## Failures and disconnection

Tickets can expire and reads are bounded to recent messages. A failed send may still have reached the service, so read the ticket before retrying to avoid duplicate updates. **Disconnect** removes Nock's saved connection and disables the integration; it does not retract text already posted or revoke credentials held by another participant.

See [Task approvals](/nock/task-approvals), [Privacy](/nock/privacy), and [Coding agents](/nock/coding-agents).