The blueprint, visualized

One diagram of the whole FoundersOS workspace setup - your agent of choice, the connectors and skills it reaches with, and the context hub that ties files, tasks, and people together.

Here is the whole setup from Getting the most out of FoundersOS in one picture. Read it top to bottom: you and the agent of your choice, the instructions that guide it, the two kinds of reach it has (connectors and skills), the FoundersOS context hub everything ties back to, and the parts that keep running on their own.

You + Your MCP client
The agent is your choice. Claude + Cowork shown as the worked example; any MCP client works.
guided by → instructions (global + project)
Guardrails
Instructions, in layers
Global house style with per-project overrides. Set once, honored every session.
the agent reaches with →
Connectors = hands
Act on a system
Live read and act access to external tools.
FoundersOS ★SlackGitHubKagiSupabaseVercel
Skills = procedures
Produce a deliverable
Packaged know-how for making things well.
docxpptxpdfxlsxresearch
★ the context hub →
Your business context
FoundersOS, anchored on a project tag
#your-project
Create the project once and its tag is auto-provisioned. From there, tagging is free: anything you tag rolls up into the project card.
Folder
Code repo plus a markdown docs repo and files, one area of work.
Tasks
Tag with #your-project, roll up automatically.
Customers
Linked to the project and to interactions.
Memory, org
Durable company brain in your own database.
Memory, personal
Your private working context, same store.
Finances, feeds
Ledger, P&L, and signal on the same hub.
and it keeps working →
Runs without you
Scheduled tasks
A morning briefing, a weekly retro, a health check, on a cadence and delivered through your connectors.
Output adapts
Rendering ladder
Same data, the richest form your client supports.
widgetinline HTMLtableprose
FoundersOS / context hub Components you arrange Examples (swap freely)

The named connectors and skills are illustrative, not endorsements. Swap in whatever fits your stack. For the reasoning behind each layer, see Getting the most out of FoundersOS; for how the output adapts to your client, see Visualizations and rendering.