How Knosy works
What actually happens between your prompt, your context, and your team.
No magic here. This page walks through what Knosy actually does at the moments that matter: when a session starts, when it learns a memory, and when your team shares context. Each section ends with the fine print for readers who want the exact mechanics.
The integration
Connecting a host adds one clearly marked Knosy entry to that host's configuration, after a timestamped backup. That entry runs at the host's official session events and is what tells Knosy a session started. Disconnecting removes exactly that entry and nothing else.
The local bridge
The hook itself is a tiny bundled program. It talks to the Knosy desktop app over a private, local-only channel and then gets out of the way. Nothing listens on the network, ever.
Your first prompt, step by step
You send your first prompt
In Claude Code or Codex, exactly like always.
The integration taps Knosy
The small Knosy entry in the host's configuration runs before the model answers, and the answer waits.
The scope picker opens
Pre-filled with the last scope you confirmed for that host and folder, with a 15-second countdown.
You confirm Private, Team, or Space
Or do nothing, and the prompt continues as Private with a notice.
Knosy hands the host your context
The scope's instructions ride along with the same prompt. Nothing is posted into the chat, and your words aren't touched.
The first answer already knows
Focus returns to the host and the model replies in context.
If Knosy isn't running, the entry finds nobody to tap and your prompt goes through immediately. Details in The scope picker.
Where the context comes from
- Each scope (Private, your Team, each Space) has one instructions file that loads automatically when a session starts.
- Every other file you've added is reference material: synced and searchable, read only when the session actually needs it.
- A session keeps its scope through resume, clear, and compact, because Knosy remembers which scope each session ID uses. That mapping holds identifiers only, never content.
How a memory is born
A session worth remembering
Knosy looks only at your prompts and the final answers. Thinking, tool calls, and transcripts are never captured.
Learning happens on your machine
Every so often, a small batch is distilled into candidate memories, locally.
Secrets are scrubbed
Clear secrets are removed on the spot. Anything uncertain goes to review instead of being published.
Published to your team
Safe, confident memories publish on their own; the rest wait for you or an Admin to review.
Found by search
Teammates find memories by searching, with their origin attached. Nothing is ever injected automatically.
How your team shares context
Your context lives in the Knosy folder
A plain folder in your home directory. Files in it are invisible to Knosy until you add them.
You edit with your own editor
Until you publish, the change is yours alone and the file shows as not yet published.
You publish, explicitly
Nothing syncs silently. Publishing is a deliberate action, with a diff when it helps you review.
Your team syncs it down
Every teammate's sessions start from the same published context.
The honest edges
- Knosy Cloud stores the current version of shared files and memories, not their history. See Beta.
- Who can publish, review, and manage is governed by your team's roles and permissions.
- Everything this page describes crossing to the cloud, and everything that never does, is spelled out in Privacy.