usewrit/writ
Writ turns a website into something you can call: read a page, collect a site, build a real API from it, or run a task on a site the user is signed in to.
Do a task on a website in a real Writ cloud browser (click, fill a form, submit, search inside an app, change a setting, book or post) and record it as a reusable workflow when it will come back. Use when the user asks for an action on a site rather than just its content, says "every time", "again", "weekly" or "record this", or wants a task on a site they are signed in to done for them.
Answer questions from data Writ has already collected, without running anything. Search across every workflow's and crawl's results, read a dataset as a table, fetch full records, shape rows for a program, and export CSV or JSON. Use when the user asks about data a Writ workflow, crawl or monitor already gathered ("what did the scraper find", "the listings from this morning", "export that to CSV"), or before re-running a job whose results may already be there.
Run Writ work on the user's own computer through a linked Writ desktop app instead of the cloud, with their own browser, logins, local vault and IP address. Use when the user says "on my laptop", "on my work computer", "from my own IP", "use my own browser", wants credentials to never leave their machine, or asks about workflows, personas, data or monitors that live on their desktop.
Diagnose and repair a saved Writ workflow that returns nothing, fails or has drifted, and edit a workflow in place (settings, persona, steps, functions, schedule and its agent skill). Use when a Writ run comes back empty or errors, a site changed, a workflow was signed out, or the user wants to change how a saved workflow behaves.
Build browserless API functions in Writ from a site's real network requests or its server-rendered HTML, so a saved workflow runs over plain HTTP with no browser and no AI. Covers capturing requests, defining and live-testing named functions, sign-in and token chains, row extraction from HTML or JSON, cursor pagination and multi-request flows. Use when turning a site into a fast, reliable API by hand, when a website-to-API build parks as needs_guidance, or when a recorded workflow should stop depending on a browser.
Buy something on a website for the user with Writ, paid with one of their cards or the card saved on the store, without a card number ever reaching the chat. Use when the user asks to buy, order, pay, check out, book and pay, or reorder something now, or to make an automation that buys (for example when a price drops), or asks which cards Writ can pay with. Writ pauses at the order button until the user confirms (email, the Writ app or Writ Desktop) unless a rule they set covers it, then Writ places the order itself.
Read web pages and collect whole sites or sections into datasets with Writ. Use when the user wants what a page says, a summary of a URL, the top N items of a listing and what each one says, several links fetched together, a page that a plain fetch could not open (JavaScript-rendered, or behind their sign-in), or every page of a site or section collected as rows to query, export or re-run later.
Work on websites where the user is signed in, through Writ personas (saved sign-in identities whose passwords and 2FA stay sealed in Writ). Use when a task needs the user's own account on a site (email, social, shop, bank, work portal), a page behind a login, a two-factor prompt, a CAPTCHA or a "confirm it's you" check, or when the user would otherwise have to paste a password or a card number into the chat.
Watch web pages for changes with Writ monitors and run saved workflows or crawls on a schedule. Use when the user wants to be told when a price, listing, stock level or status changes, wants a page checked every few minutes, or wants data pulled every morning or every hour. What happens after a change or a scheduled run (notifications, chained workflows, digests, an AI agent) is the writ-automations skill.
Turn a website into a callable API with Writ, then run, prove, publish and repair it. Use when a site has no official or practical API but the user wants its data or actions programmatically ("turn this site into an API", "an endpoint for", "map the API of"), wants something their code, spreadsheet or another agent can call later, or wants to run a saved Writ workflow and get its data.