Use cases

Use cases

What people use Onlay for, one page each: the problem, the commands, what readers do and what comes back to the agent.

For agents: this page as Markdown · llms.txt

• Give feedback on the mockups and prototypes your agent builds
  Your agent builds a screen, a flow or a prototype as HTML. Point at what is wrong, on the page itself, and the agent gets the exact element and your words back.
• Share an HTML report with your team and collect their comments
  Your agent wrote a report as HTML, with tables and charts. Send your team one link, let them comment on any number or sentence, and have the agent revise it from their feedback.
• Review an HTML slide deck with comments on each slide
  Your agent built a presentation as one HTML file. Share it, let reviewers comment on any slide, title or chart, and have the agent revise the deck at the same link.
• Get comments on a Markdown plan, spec or PRD your agent wrote
  Your agent wrote a plan or spec in Markdown. Publish it as a clean, readable page, let reviewers comment on any line, and give the agent their feedback anchored to the source lines.
• Let people fix the wording of an AI-written document themselves
  Instead of describing a change in a comment, a reader clicks the sentence and rewrites it. The agent gets each edit as the old text and the new, and applies it to the source.
• Collect comments on a website or web app your agent built
  Publish a static site or built app as a folder, or add one script tag to an app you deploy yourself. Reviewers comment on the real pages; your agent gets each thread with its page and, with the build plugin, the file and line that drew it.
• Ask people to choose, and let your agent read the answers
  Your agent builds a page that asks a question (a poll, a set of options, a slider) and shares it. People answer on the page; the agent pulls the answers with who gave them and acts on the result.