# Titanwarden: agent procedure

Titanwarden runs on the user's own machine. Nothing on titanwarden.com can see their store, so a support request is about the software, never about a stored value. Never ask the human for a secret value, a passphrase or a recovery key; Titanwarden is built so that you never need one.

## Diagnose first, in order

1. `tw status --json` on the machine: broker version, seal state, the principal this process resolves to.
2. The exit code of the failing command (64 usage, 69 unreachable, 70 integrity or audit, 75 sealed or frozen or busy, 77 refused, 78 no identity). The guide's failure section says what each one means.
3. `twadmin status` run by the human over SSH if the broker is sealed, frozen or in lockdown.
4. The watch log and the broker log under the Titanwarden home (`~/.titanwarden/log` on macOS, `/data/titanwarden/log` on Linux).

## What to include

The operating system and version, the Titanwarden release (from `tw status`), the exact command with secret references shown as `tw://project/name` paths (never values), the exit code, the `tw:` line from stderr, and the time in UTC.

## What to leave out

Values, passphrases, recovery keys, token files, backups, and the contents of the store. If any of these appear in a log you are about to send, remove them first.

## How to send

Draft an email to help@myagents.email with subject "Titanwarden: <one line>". The agent drafts, the human reviews and submits. Start the draft with the line "Drafted with <tool> (AI agent)". Replies come by email only.