Docs
Refer a friend. Get a weekly-quota reset.Friend signs up and uses it → +1 reset (valid 30 days) · up to 10% cash back on their spend.
+1 resetGenerate link

Data, deployment and recovery

Distinguish local and remote deployment and understand keys, history clearing and recovery.

Local and remote deployment

Use wrok-bot-server --local for local single-user work. Remote service remains on loopback behind a same-machine TLS proxy. Set WROK_BOT_PUBLIC_URL and a securely generated 64-character lowercase hexadecimal WROK_BOT_TLS_PROXY_SECRET known only to proxy and server.

The proxy must discard client-supplied x-wrok-bot-proxy-secret, x-forwarded-proto and x-forwarded-host, then set the shared secret, https and exact public authority, including an explicitly configured port. Forward only traffic actually received over HTTPS. A public URL alone is not authorization.

Data and keys

PostgreSQL data, application keys, Vault credentials and release identity are linked. Do not generate a replacement key over existing data, delete locks or mix another installation's directory while troubleshooting.

History and artifacts

Closing history, draining runs, clearing text, deleting artifacts and restoring are distinct operations. Mainline has limited implementations, not complete acceptance of every GUI and recovery journey. Check target, authority, active work and retention before acting.

Recovery

Desktop whole-PostgreSQL restore has reached main, while two-account platform rehearsal and OS credential checks remain open. Use a matching release, a verified backup artifact and its recovery procedure. A test fixture or copied database directory is not an accepted recovery backup.

Diagnostics

Preserve version and relevant errors while excluding credentials and private content. Investigate unknown or unready states instead of disabling checks to force availability.