Personal AGI won't arrive as a better chatbot, rather it arrives as an agent that knows the full state of your work -very person, your every project, every promise - and acts on it That is ShogunAI: general across your work rather than narrow to one task, and living inside your PC rather than someone else's cloud it builds that state as you work, keeps the evidence behind every record, and spends it finishing real work. Reading is automatic. Sending always waits for your approval, macOS today.
HI, Product Hunt
first of all, a definition, since the term is doing a lot of work in our tagline
By personal AGI I don't mean human-level intelligence rather i mean general across your work rather than narrow to a single task
its one agent that spans your whole day, holds the state of it, and acts on that state
the bet underneath is this-
The models are already smart enough for most of what you do, what they're missing isn't IQ it's you and the memory of what you do,
your context is scattered across a dozen tools, and the only thing holding it together is your own memory and your patience
You re-explain the project, paste the thread, repetitively remind it who this person is, and then do the last mile by hand anyway.
the bottleneck moved, and most products haven't
I don't think I'm alone in reading it that way
Garry Tan has stressed upon it this year telling founders that the leverage sits in your context rather than in the model
same weights, same window, yet wildly different output depending on what surrounds it.
even Sam Altman keeps describing where OpenAI is going in nearly the same terms: less chasing raw IQ,and more of understanding your whole context and remembering it, with that memory as the durable advantage.
When the person who sees the most startups and the person shipping the most-used model arrive at the same layer from opposite directions, the layer is real
which leaves the question that actually matters-
where should that context live?
and that's where we answer differently
ShogunAI keeps one state of your work,-
the people, the projects, the promises, the things still open- all assembled from your very own day and held inside your own machine rather than in someone else's account.
then it spends that state on finishing tasks
The reply arrives already drafted, knowing what you promised last month. A meeting ends with the next step instead of a transcript. The morning opens with what moved overnight and what needs to be done ahead
you bring your own model, and you keep the memory either way
One rule I won't trade away: reading is automatic, sending never is
Anything addressed to another person stops and waits for your approval
Today it's built for one person,which is you
Team and enterprise plans are on the roadmap, because shared context is worth more than private context, and most of the work that gets stuck is stuck between people
The build that runs today is macOS; Windows and mobile are being built.
What I'd genuinely like from this thread:
Tell me where the argument breaks. Is context really your bottleneck, or is it something else entirely?
Tell me your version of the problem -what you find yourself re-explaining every week
Tell me which integration would decide it. Name the tool that has to be connected before this is worth having, and it moves up the list
And tell me honestly- would you leave something like this running for a full week? If not, what stops you?
Report
proud to have contributed towards making ShogunAI. the models were competent, yet I had to do all the workflows by repeatedly copying context and introducing people.
what is most important about it is that it keeps track of the context and uses it to accomplish work, at the same time keeping the border clear: it can read automatically, but nothing is sent out until authorized.
waitlist is LIVE, and we're rolling out beta very soon!!!
Report
Maker
@githubanant I remember the day when you—one of our first test users—were so impressed by the MVP that you told us you wanted to work with us.
We’ve made tremendous progress, but there’s still a long way to go.
Let’s build a great product together!
Report
Maker
Also, since I often get asked about this, I’d like to share a blog post explaining why the name became “Shogun AI.” Please check it out and let me know what you think!!
proud to have contributed towards making ShogunAI. the models were competent, yet I had to do all the workflows by repeatedly copying context and introducing people.
what is most important about it is that it keeps track of the context and uses it to accomplish work, at the same time keeping the border clear: it can read automatically, but nothing is sent out until authorized.
waitlist is LIVE, and we're rolling out beta very soon!!!
@githubanant I remember the day when you—one of our first test users—were so impressed by the MVP that you told us you wanted to work with us.
We’ve made tremendous progress, but there’s still a long way to go.
Let’s build a great product together!
Also, since I often get asked about this, I’d like to share a blog post explaining why the name became “Shogun AI.”
Please check it out and let me know what you think!!
https://shogunaios.com/en/blog/the-shogun-was-never-a-king