› Rework the launch positioning.Reading the project and its decisions…✓ Context recorded with its source.
AI second brain / personal agentic OS
Agents that start knowing your work.
Shedu turns the work you already do into context every agent can use. Plain files on your own server, kept current automatically.
Built for solo founders who run their work through Claude Code, Codex, and AI coding agents.
But today, every session starts cold.
A smart agent with no history is a new hire on day one. Your context exists; it is stranded where no agent can reach it.
decisions/launch-positioning.mdin an old session
you/voice.mdin your head
last week’s claude sessionexpired
client call notessomewhere in drive
positioning(old).mdwhich one is current?
● your agent · new sessioncontext: none
› Continue the launch positioning work.
Which project? What was decided? Whose voice?
No memory of previous sessions found.
Re-briefingYou explain the project again, every single session.
Lost decisionsThe reasoning lives in a session that is gone.
Generic outputIt knows the internet, not your business.
Every cold start makes you pay again for context you already produced.
The DIY fix becomes a second job.
Folders, prompts, memory tools, scripts. Soon there are five versions of the same truth and no route to the current one.
Enter
shedu
One system that captures your work, files it with its source, and briefs every agent you run.
Work in. Context ready. Better work out.
The system in three steps: your AI sessions, the things you send, and your connected services flow into your second brain automatically. The brain files everything into plain, routed files. Every agent then starts briefed and produces your work instead of generic output.
Notion
HubSpot
Slack
Gmail
Google Drive
Google Docs
GitHub
Linear
Google Meet
CaptureSessions, links, notes, and services flow in as you work. Nothing to feed.
FileEverything lands in plain files with its source attached.
BriefEach agent reads only what its job needs, and starts current.
A folder your agents understand.
Plain files that update themselves. Read them, search them, point any agent at them.
Take the files and go whenever you want.
~/your-systemowned by you
▾projects/work + decisions
▾people/history + commitments
▾you/voice + opinions
▾methods/how you work
▾sources/where it came from
◆agents.mdhow agents navigate
◆index.mdwhat matters now
Your server. Your agent. Your files.
A private VPS with a Hermes agent on duty 24/7. Your credentials never run on infrastructure you do not own.
Private VPS
Hermes is on duty.
- VPS accountYours
- System filesYours
- CredentialsYours
- Custom MCPsIncluded in handoff
- Our accessYou decide
- ExitTake everything
Two ways to run it
01Full handoff
Set up and hand over
We build it, document it, and step away. You run it privately.
- Every credential handed to you
- Our access ends at handoff
02We stay on
Owned and managed
You keep ownership while we maintain the system for you.
- Ownership stays with you
- Access agreement you control
Who it’s for
Built for people already running real work through agents.
This is for you
A coding agent is one of your main work surfaces, and you pay the re-briefing cost every day.
This is early for you
You use AI occasionally, or you are looking for a note-taking app.
Fair questions, straight answers.
Yes. It is an AI second brain designed for agents as well as people. It captures the work you already do, keeps that context organized in plain files, and gives each agent the material relevant to its job.
Yes. The full system combines your living context, routing files, custom MCP connections, and a 24/7 Hermes agent on a private VPS. “Custom context system” describes the core underneath it.
The files, VPS account, credentials, agent configuration, routing system, and custom MCP connections built for your workflow. The system remains useful outside a Shedu relationship.
You choose. In handover mode, we finish the setup, give you the documentation and credentials, and relinquish access. In managed mode, access is limited to the maintenance arrangement you approve.
Yes. The DIY stack is the real alternative. A custom build buys the organizational principle, routing, integrations, implementation, and upkeep that keep the file system usable as it grows.
The build is designed around the sources and services that run your business. We create the MCP connections required for the agreed workflow instead of forcing every client into the same integration bundle.
Take the files, server, configuration, and credentials with you. They are already yours. A plain-file system gives your current and future agents a durable place to start.
One context system, ready in 14 days.
The Shedu Founding Build
All your context captured in one place, ready for every agent you use.
€2,500Founding pricefuture builds from €5,000
14 daysImplementationfrom payment to handoff
30 daysSupportfree updates after handoff
Start your Founding Build
One 30-minute call with Cha scopes the build against your actual stack. No application, no reservation.
Implementation starts when payment clears and every agreed access is in place.
No required management subscription. You can run the system yourself after handoff.
Copy-architecture prototype. The build call books directly through Calendly.
Not ready? Keep me updated.
We publish what we learn building systems like this one, so you can build your own. The guides arrive as they ship.