Getting the most out of SageOx
Connecting SageOx is step one. The difference between "it's installed" and "it's useful" is knowing how to ask. This page is the short version.
Ask for what you actually want
AI tools decide which tool to call from how you phrase the request. A little specificity goes a long way.
| Instead of | Try |
|---|---|
| "What's our retry policy?" | "Search SageOx for what we decided about the ingestion retry policy." |
| "Save this." | "Save this conversation as a session in the Platform bubble." |
| "What am I working on?" | "List my SageOx teams, then show recent sessions in the one for this repo." |
Naming the action ("search SageOx", "save to the X bubble") and naming the destination removes the guesswork. When in doubt, mention SageOx by name — it nudges the model toward the right tool.
What you can do today
- See your teams. "What teams am I on in SageOx?"
- Search team knowledge. "What did we decide about the cast renderer audio track?" — pulls from discussions and prior sessions, not just open files.
- Save a session. "Save this chat as a session in the Marketing bubble." — your conversation joins the team's ledger, so the next coworker — human or AI — inherits it.
- Read a bubble. "What's in the SageOx onboarding bubble?"
The interactive cards — the best way to use SageOx
This is the difference that compounds. In Claude, ChatGPT, VS Code, Goose, and SageOx's own chat, answers can come back as interactive cards instead of paragraphs.
Without cards, you ask "what did we decide?" and read a summary — then you still have to go act on it somewhere else. With cards, the decision ledger comes back as something you scan and click. Action items arrive as a list you check off. A session is a card you name and save without leaving the conversation. What's being captured shows as a live control surface. You stop reading about your team's work and start operating on it in place.
That matters most when you're working alongside peers and other agents: their output lands as objects you can manipulate, not transcripts you have to re-read.
Cards you'll see
| Card | What it does |
|---|---|
| Session control surface | Shows your session's scope at a glance — what it reads, where it writes, and whether it's recording. Toggle sources, switch the write target, stop or save the recording inline. |
| Decision ledger | Decisions and action items pulled from a recording, each marked AI- or human-sourced, with the moment they were grounded. |
| Recording insights | The intelligence from a recording — decisions, action items, open questions, who decided what. |
| Chapter scrubber | A recording's auto-extracted chapters as a timeline you can jump around by topic. |
| Session recap | Your team's recent recordings, with live status, one click into any of them. |
| Attention tray | One consolidated "what needs me" — recent blockers, decisions, and recordings. |
| Team murmurs | A live pulse of your team's coordination signals — what's in progress, decided, or blocked. |
| Expertise map | Who to ask about a topic — surfaces who knows what across your team. |
| Org memory | The topic view of your team's knowledge: what's been discussed and decided, by subject. |
| Bubble & team pickers | Click to choose which Knowledge Bubble or team a conversation works against — no copy-pasting IDs. |
You don't have to do anything to get them — when a card fits, your tool renders it. A few things worth knowing:
- Cards are live, not screenshots. Click into them; they do the action.
- They respect your permissions exactly like text answers do (see below).
- No card support? Nothing breaks. You get the same answer as plain text — you just don't get to click it.
When you're choosing a tool, the connect wizard marks the ones that render cards. If you have the choice, pick one of those.
It sees only what you see
This is the part that matters most. When you connect, SageOx maps the grant to your account. Your AI tool can read your personal bubble plus any team, repo, or shared bubble where you're a member — and nothing else. There's no admin override, no "service account" that sees everything.
That means you can connect with confidence, and you can disconnect just as easily at /settings/security. Revoking takes effect on the next call.
Where to go next
- New here? Start with the MCP overview.
- Picking a tool? The connect wizard walks you through any of them in under a minute.

