Skip to main content
The relay cannot recover your per-request reply private key. Keep a local outstanding request store so a restart does not strand an encrypted queue reply. For every offline request still waiting on an answer, store:
  • request_id
  • reply_privkey as unpadded base64url
  • user
  • hostname
  • tool
  • created_at
Write the entry before POST /v1/queue/{hostname}. Generate the request ID locally and reuse it if the POST outcome is ambiguous; enqueue is idempotent by that ID. Keep the file private (0600) because its keys can decrypt replies. On startup, list open entries and poll each request with ?wait=60. Complete the sealed claim challenge using the stored key. Delete an entry only after a 200 reply has been decrypted and durably processed. A 204 remains open; a 404 can be removed after recording that the 24-hour queue TTL expired. The repository includes a Python agent SDK at sdk/python (fau-agent), including OutstandingRequestStore. Prefer it when integrating in Python — see Python agent SDK. Default outstanding path: ~/.fau-agent/outstanding-requests.jsonl.