SaaS ideas your next customers are already looking for
100 SaaS startup ideas for the people who said they'd pay, from agency owners to dentists. Micro SaaS ideas, AI SaaS ideas and B2B SaaS ideas: find yours, build it, sign them up.
Popular:
| # | Idea |
|---|
No idea matches this filter.
Pain points in business: what people struggle with
Search the problems to solve, as people described them on Reddit and other platforms, in their own words.
Popular:
| # | Pain point |
|---|
No pain point matches this filter.
AI Agent Crash Recovery
Long-running AI agents lose state, duplicate side effects, and cannot safely resume after crashes or failures.
In their words
whenever I do a test group, for many of the users by the time they get to use it, the connections have gone stale
Cancellation tokens are not carrying across the queue boundary, spans close without a shared reason and token costs show up after the interface says the request failed.
when one person's agent produces something another person's agent needs, the handoff is just... a human relaying it
when it freezes in a subagent, I don't see any way to stop and continue that subagent
keeping state persistence across long running tasks is such a headache
the biggest pain point im dealing with is state management between runs, if you can solve that cleanly i think many developers would pay
workers AND SCRIPTS can't just be waited on, instead the model has to keep checking in
What still goes missing for me is the *state of decisions*, which isn't the same thing as the conversation.
This constant polling requires literally millions of input tokens. Even if it's cached, it eats up the quota like there's no tomorrow.
Figuring out where to resume without repeating work or skipping steps is harder than it sounds and most frameworks leave you to sort it out yourself.
I'm constantly using /remote-control for Claude code but it isn't seamless as I want it since it's still needed to be revived for every Claude desktop restart
Half the time it just moves on like nothing's pending.
I often want to have agents stop at certain points, but fail to get a mechanism that works.
I now treat any artefact that two agents can both access as a coordination problem, not a storage one.
AI agent developers
Where they talk
- r/AI_Agents
- r/hermesagent
- r/ClaudeCode
- r/ClaudeAI
- r/LangChain
- r/aiagents
- r/LLMDevs
- r/codex
Tools they use today
- Claude Code
- Hermes
- Codex
- git
- LangGraph
- Claude
- MCP
- PostgreSQL
Why those fall short
- no event-based callback; agents ignore instructions and keep polling
- Files hold what was decided, not whether it shipped or what supersedes what
- sessions tied to browser/TUI; background tasks stop with parent; no resume
- Connections time out; users must re-authenticate; support suggests API workarounds
- rules stay unreliable and inconsistent; still draining quota
Map of ideas
Drawing the map…