API key rejected
Check the key was copied in full and hasn't expired, or create a new one in the Anthropic Console. Type dryrun instead if you just want to see how the tool works, at zero cost.
Products · LyttonOS AI (Alpha)
Help make LyttonOS AI better
If something went wrong for you, the troubleshooting below is the fastest way to get unstuck. If you want to see what's already known and logged — or tell us what else to build — that all lives on Product Lab now. What's here is what this page can do that a bug tracker can't: explain why the loop back from you to the next version matters at all.
Something went wrong?
It's taking a long time, or failed after a long wait
A long job description with a lot of legal or HR boilerplate slows things down. Strip that out before pasting and try again — see how it works for more detail.
The reply wasn't valid, or looked cut off
Occasionally the model's reply doesn't parse cleanly. Re-running the same input usually resolves it. If it happens twice with the same CV and job description, that's worth reporting below.
Not covered here, or need a human? Get in touch directly.
Why the feedback loop is part of the plan, not an afterthought
A go-to-market plan usually stops at launch: get the thing in front of people. The harder discipline is what happens next — building a real path from what people actually hit, back into what gets built or fixed next, and closing that loop on a cadence rather than waiting for complaints to pile up.
That's why every piece of feedback on LyttonOS AI goes to one person, by name, not into a ticket queue — and why what's known and logged is visible on Product Lab rather than sitting in a private backlog. Think First. Then Automate. applies here too: understand what's actually breaking, for real users, before deciding what to build next. A feedback loop nobody can see isn't a feedback loop — it's just note-taking.