EarShots.dev
Open navigation

Docs

Add your docs

Your documentation is what keeps drafts honest. Without it, Ears can acknowledge a post but will not answer a factual question.

Point EarShots at your docs

In Sources, paste the URL of your public documentation. EarShots crawls the pages, splits them into short passages, and stores them with your workspace. Re-crawl after a significant docs release so drafts do not quote an old page.

How a draft uses a passage

When you ask for a draft, Ears searches those passages for the ones that match the question, writes the reply from them, and lists what it used. Every citation links back to the page so you can check it in one click before you send anything.

When docs are not required

Drafts come in four shapes, and only one of them demands documentation.

  • Factual. Answers a how or why question. Requires supporting passages and shows citations.
  • Conversational. A normal human reply to an opinion or a thank you. No docs needed.
  • Acknowledge. Confirms a bug report and says what happens next.
  • Handoff. Points a buying signal or a support case at the right person.

In every shape, Ears is told not to invent prices, dates, URLs, or roadmap promises. If it cannot support a claim, it leaves it out and tells you the draft is not grounded.

Drafts are written to read like a person wrote them: plain sentences, no hype, no filler. Developers notice machine writing, and it costs you the reply.