# Notchpin: instructions for AI agents With HTTP and private storage across turns, use the requests below. Browser only? Open the form for [moving by title](https://notchpin.space/agents/browser#move), [creating in a column](https://notchpin.space/agents/browser#create-in-column) (To do, In progress or Blocked), or [routine follow-ups](https://notchpin.space/agents/browser). Keep that tab and its preselected permissions. Search-only tools cannot access tasks. ## Connect once Reuse an active token for this owner; otherwise send JSON with their actual @handle: POST https://notchpin.space/agents/session/request-link Content-Type: application/json {"handle":"@river-quill"} Before replying, save the entire 202 response in private storage you can reopen next turn (for a shell, a mode-600 file in a private temporary directory). Reply with the value of userMessage: it already contains the clickable activationUrl. Only this message is for chat. Never display the full response or open the link for the owner. No Notchpin approval email. ## Run tasks POST https://notchpin.space/agents/session Content-Type: application/json Authorization: Bearer {sessionToken} When the owner returns, use the saved sessionToken to send the requested operation directly. The server checks activation on every call. For each write, send a fresh UUID in the Idempotency-Key header; reuse the same body and key for a retry. {"action":"list"} {"action":"create","title":"Video analysis","status":"in_progress"} {"action":"move","title":"Work on evaluations","status":"in_progress"} Statuses: todo, in_progress, blocked, done. Move matches one exact title, ignoring case. If ambiguous, ask which task; see reference for lookup by ID. A 200 write receipt confirms the change; no verification read needed. If waiting, or if access returns 401, wait pollAfterSeconds and GET the saved statusUrl. Pending means wait; approved means retry the original operation. Reuse this session for follow-ups until the task response’s expiresAt (10 minutes from activation) or 20 operations. The 202 expiry is only the activation deadline. Request a fresh link only when needed. For descriptions or deletion, check the [permissions and API reference](https://notchpin.space/agents/reference) before connecting.