FAQ

FAQ

Does anything leave my machine?

No. There is no analytics or error-reporting client anywhere in the coordinator or the extractor. Your data is one SQLite file on your disk, your agents browse from your IPs, and OCR runs locally — the model weights ship in the wheel, so it works air-gapped.

Does replaying a workflow cost AI tokens?

No. Recording uses AI once, to understand the page. Replay executes the saved step list — a daily monitor costs nothing to keep running, whether that is run 10 or run 10,000.

Do I need an AI provider at all?

Only to record or to use the AI features. Replaying, scheduling, monitoring and crawling need none.

Why is nothing running?

You almost certainly have no agent connected. The coordinator runs no browsers itself. See Connecting agents.

Can the coordinator run the agent for me?

Not from Docker — a container has no host process table or browser runtime. Use the one-line installer on the machine that should browse. A run-local.sh install can, from Fleet → run an agent on this host.

How many agents can I run?

As many as you like, anywhere. They dial out, so no inbound ports and NAT is fine. Work spreads across whichever have capacity. Scale browsing with agents — never with web workers, which the coordinator refuses.

Is there a paid edition of this repository?

No. There are no feature gates in the self-host build. A hosted product exists; this repository is not a trial of it.

Does it work behind a corporate proxy / air-gapped?

Agents make outbound HTTPS/WSS only. OCR is fully offline. You need network access to fetch the agent binary and Docker images once; after that the extraction path needs nothing external.

Can I use Postgres instead of SQLite?

The shipped product is SQLite and that is what is tested and supported. The test fixtures accept a postgresql:// DATABASE_URL for contributors, but running the coordinator itself on Postgres is not a supported configuration.

Where are my screenshots stored?

On the data volume, when WRIT_FILES_DIR is set — which the shipped compose does. Leave it set; without it they are base64-encoded into the database.

I forgot the admin password.

There is no email reset. See Backup and restore.

Can I rebrand a fork?

The code is AGPL-3.0 — fork it freely. The Writ name, wordmark, glyph and tile are trademarks and not covered by the AGPL grant; read THIRD_PARTY_NOTICES.md before rebranding. If you deploy a modified build, set WRIT_SOURCE_URL to your own repository — that is the one thing AGPL §13 requires of you.

How do I report a security issue?

Privately, not as a public issue.