Question 1

Do we have to rewrite the SDK?

Accepted Answer

No. You wrap the CLI, hang middleware on the API, or register one file in Next.js. The probe watches failures. It does not sit in your hot path as a new product surface, and it does not ask you to change how developers already use your tool.

Question 2

What does the developer actually see?

Accepted Answer

A short question in the terminal or the SDK error UI. Not a chatbot landing page. They can answer in a sentence. If they walk away, you still have the stack, the OS, and the command they ran.

Question 3

Do tickets go out on their own?

Accepted Answer

No. AethelLayer drafts GitHub and Linear. You approve. Same rule as the rest of how we work: agents propose, humans ship.

Question 4

What do you store?

Accepted Answer

Hashed identifiers, runtime, OS, the error, the thread, and optional session links. Not source code dumps. Not secrets you did not already print to the terminal.

Question 5

How fast is a real install?

Accepted Answer

Most teams are live before lunch. The 60-day pilot is for teams who want us in the repo, writing the taxonomy with you, not a slide about it.

The questions we get on the first call.

Stop finding out about churn in a dashboard three days later.