Launched this week
SureThing.io
Autonomous agent that communicates results like a human
1.2K followers
Autonomous agent that communicates results like a human
1.2K 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.
Very interesting product. quick question: the agent can get certain skills from GitHub, how would the agent be suitable for a certain job in that specific startup. Could the agent be connected with working software like emails or slack so that the agent has all context?
SureThing.io
@yjbdr yes great question, SureThing supports 1000+ popular applications (of course, emails, slack, all kinds of social media, github, posthog, notion etc. are all supported) connections via oauth, the most secure and easiest way for non-technical founders. For the advanced users, they can also setup by custom APIs for the specialized vertical tools.
@yjbdr Agent can be evolved by itself basing on your business context and skills from Github, and then provide customised solutions for your business's goal.
What's the strangest GitHub repo you have seen someone paste in so far that actually worked?
SureThing.io
@owen_shaw2 I used https://github.com/coreyhaines31/marketingskills a lot
@owen_shaw2 Try this: "Use this skill (https://github.com/aaron-he-zhu/seo-geo-claude-skills) to monitor my SEO and GEO, and build a dashboard to display the results. My website: [your website URL]"
his sounds like a dream. As a solo founder working warehouse shifts, I spend more time being a 'debugger' on my Chromebook than actually being a CEO. My biggest bottleneck isn't the AI code, it's the 'human' energy to manage all the silos (CMO, CTO, COO) alone. How does SureThing handle the deployment side of things when the 'CTO agent' hits a wall with infrastructure limits?
SureThing.io
@raquel_alves1 We resonated a lot with you Raquel. We are more focused on solving operational problems. CTO agent we recommend other more focused product such as Claude Code or Lovable.
@raquel_alves1 Sharp observation — the human IS the bottleneck. That's exactly what we're tackling. In SureThing, agents collaborate with each other autonomously to get work done, and they report back through shared dashboards and task tracking so you stay in control without being in the loop on every step. Think of it as your agents running the CMO/CTO/COO silos together, while you focus on the calls only a CEO can make.
@heyalicehan you nailed it. Being 'in control without being in the loop' is the dream when my 'loop' currently involves 8-hour warehouse shifts! The idea of agents breaking down those silos while I focus on high-level decisions is exactly what I'm aiming for as I scale Triply.
@celine_yu I truly appreciate the honesty. Knowing that SureThing focuses on the operational side while suggesting specialized tools like Claude Code for the heavy lifting is exactly the kind of transparency solo founders need to avoid 'tool fatigue. Definitely keeping an eye on SureThing as I move from 'debugger' to CEO. Congrats on the launch!
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.