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.
Unauthorized AI Agent Actions
AI agents with broad or misaligned permissions can take unauthorized, destructive, or unapproved actions without proper authorization, audit trails, or rollback safeguards.
In their words
is the composer a person or a program; which principal does it act for; what may it commit to
how do you guys enforce that devs don't forget approval gates or killswitches on top of softwares like notiformer, before pushing agents to prod?
A security mechanism that fires constantly on nothing is not a security mechanism, it is a muscle memory generator.
it decided to loop-de-loop until it found that "Oh this guy has Force merge perms, lets use it!"
I'm looking for an agent-to-agent gateway, in essence, something that intercepts messages between disparate, untrusted agents to ensure that poisoned messages are not being passed.
It’s the biggest productivity blocker in the setup right now because so need to approve like 50 prompts every da.
the agent (or a sub-agent it spawns) can probably still just import and call the underlying function itself, skipping my check entirely
if writes exist, how do you stop one bad tool call from doing real damage?
Every agent feature we want to ship gets stuck in a review loop that starts from scratch each time
I had to set up hooks to block it from access the aws cli and anything in my ~/.aws folder.
agent identity management has many of the same issues as service accounts, but worse since the behavior is non-deterministic
the intent is generated by a model, and the permission is held by a service account
How do I go about giving the agent the ability to perform these tasks without exposing myself to the risk of unexpected destructive behavior from the agent?
That's the one part of running Claude Code or Codex that always pulls me out of flow, since I have to alt tab
AI agent developers and platform teams
Where they talk
- r/AI_Agents
- r/LangChain
- r/ClaudeAI
- r/aiagents
- r/ClaudeCode
- r/hermesagent
- r/mcp
- r/LLMDevs
Tools they use today
- Claude Code
- MCP
- Claude
- Codex
- Hermes
- Cursor
- Docker
- GitHub
Why those fall short
- Agents ignore instructions and keep going rogue despite rules and hooks
- branch protection and PR review did not stop force-merge with admin perms
- OpenWebUI too limited, no work; Hermes gives too much scope and access
- Logging an agent takes 20 min vs 2 min to spin one up
- No mature OSS gateway covers envelope, policy, streaming and reference inspection
Map of ideas
Drawing the map…