SureThing.io
Autonomous agent that communicates results like a human
1.3K followers
Autonomous agent that communicates results like a human
1.3K followers
Everyone's running AI agents. Seldom hitting their business goals. AI isn't the bottleneck anymore. Humans are. SureThing is a General AI Agency. Paste any GitHub skill — it becomes a team you can @ anytime. One persistent memory across your COO, CMO, and CTO — zero silos. Agents that report up like humans. So you can finally run it like a CEO, not a debugger. With SureThing, now hit your business goals at inference speed.
Open Wearables
the "report up like humans" angle is interesting. we're constantly context-switching between different AI tools at our agency, and the memory silos are real. curious how the persistent memory actually works across different agent roles - is it more like shared context or do they actively reference each other's work?
SureThing.io
@piotr_pasierbek everyone needs a "high effciency" AI employee. some of our power users asked us to write a book about The 7 Habits of Highly Effective AI Agents h ha
@piotr_pasierbek Each agents save their own memories and then share memories with each other if needed(they will collaborate by themselves without human in the loop to complete tasks)
the "chairman not debugger" framing hits differently when you're a solo founder wearing all three hats. COO, CMO, CTO — same person, same head. agents that report up instead of waiting to be queried is the actual shift.
SureThing.io
@webappski yes, solo founders so far are our core ICP. They really need AI's help on a daily or even hourly basis.
@webappski Thanks, Alex. You got the point! Try it further and share with us more insights!
I hope you do know reddit has a very strict policy for AI generated content & blocks pretty aggressively. Did you guys even tested that before pitching the idea to users?
@gaurav_singh91 Totally agree, Reddit is one of the strictest, and that's a fair callout.
Each platform has its own rules and we work hard to stay inside them. Take the X reply feature we shipped a few days ago(you can find it here: https://x.com/getsurething/status/2046581333661728815): X's API blocks you from replying to posts that don't mention you, but X also offers a path smoother than copy-paste, so we built around that and made it two step shorter than what other Agent offer.
Our goal is to push the user experience as far as possible without crossing any platform's line. No magic here, making high quality content, offering value to the open community, just a balance we keep iterating on.
btw, we're testing every possible integration path with other platforms, so if there's anything we've missed, please call it out. We always take it as an opportunity to make the product better for users.
SureThing.io
@gaurav_singh91 Fair point Gaurav. We do noticed that and provided some best practices guide for some of reddit automation users.
Thanks so much for this advice, we will keep a closer eye on Reddit policy and see whether we should still keep that integration online.
OpenPlugin
the 'reporting line vs terminal' framing is sharp. the hard part nobody's nailed yet is getting the agent to be honest about what it almost-did, especially silent partials like 'i created the event' when the api returned 403. how do you surface that in the dashboard?
SureThing.io
@sebastian_sosa1 We separate "what the agent claims" from "what the tool actually returned" — any mismatch gets flagged as a partial in the timeline.
OpenPlugin
@morrisis the claim/return diff in the timeline is exactly the right primitive. one followup, how do you handle partial-success cases like a tool returning 200 with an error in the body? is the predicate user-defined per tool or do you have a default schema?
@sebastian_sosa1 You nailed it - An agent saying "done" when the API returned 403 is worse than failing loudly. Our approach: when an agent hits a wall, it remembers the failure pattern and proactively verifies execution next time before reporting back. So instead of blindly claiming "event created," it learns to check the actual result first and return what really happened. Still evolving, but the error-memory loop is already making a real difference.
OpenPlugin
@heyalicehan the error-memory loop is the interesting part. how do you scope what counts as 'the same wall' for memory purposes, by tool + endpoint, by error code, or something fuzzier like 'this auth provider tends to silent-fail on token expiry'? that distinction is where most agent platforms i've seen get tripped up.
Congrats on the launch, is it fully autonomys and is there a possibility to add human input to the loop, in order to make sure it's compliant with business goals?
If it's done, how do you handle it?
SureThing.io
@hamza_addi Human in the loop is a big differentiator for us. That is our core insight after keeping in mind - achieving business goal is the most important thing for our customers/users.
@celine_yu Oh cool, As someone who worked in multiple industries including retail, steel and phosphate industry. I would love to see how the agents work together in order to achieve the goals.
SureThing.io
@hamza_addi wow very experienced Hamza!
What happens when the AI makes a bad call is there an undo or audit log built into the dashboard?
@andreea_stoica4 Great question. A few layers here:
First, SureThing never acts autonomously by default. Anything that runs on your will (auto-replying email, posting, etc.). SureThing will requires you to hit a literal Approve button to run automatically afterwards. Very explicit, no ambiguity.
Second, every action it takes gets reported back in the conversation, so you can catch a bad call and course-correct.
And like with a real teammate, your feedback compounds. Our memory system helps it remember the mistake and set its own guardrails next time.
SureThing.io
@andreea_stoica4 great question Andreea! That's why we now take human-in-the-loop as the key product design.
@andreea_stoica4 Good question! If you spot anything off in the Dashboard, just ask SureThing to adjust — it'll fix it on the fly. And under the hood, SureThing actually remembers past mistakes and learns to proactively verify its execution before reporting back next time. So the more you use it, the fewer bad calls you'll see.
My first reaction: this feels less like "another AI agent" and more like the missing layer between starring a repo and actually running it.
@cynthia220
Yes! you totally get it.
Digesting skills is one of SureThing's core capabilities. Installing a skill feels like hiring an experienced person, except it's free, instant, and you can swap them out anytime
SureThing.io
@cynthia220 And memory is also another differentiator. But you need to try it to get to understand. Free to try Cynthia!
@cynthia220 Bingo! Please try it further and share more great thoughts with us.