Change who can read your sessions
Who can read a session is decided twice: once by your default when the session starts, and again whenever you change it on the session itself. Storing is separate; a hidden session is still stored
Your default audience
Section titled “Your default audience”New sessions take the default from your active profile. Setup asks for it: the desktop app’s setup under Who can read new sessions, and the web app’s first-run page under “who can read new sessions”. The desktop app names the values Only me, People I share a project with, Everyone in the account, for <owner> repositories and Everyone in the account. The values:
| Value | Who can read a new session |
|---|---|
private | Only you |
project | Members of the projects that hold the repository. Team and Enterprise plans |
org_public | Everyone in your organisation, for the organisation’s own repositories; a session in a personal or unrecognised repository stays private |
public | Anyone signed in to your workspace. Not the open web |
kcap config set default_visibility org_publickcap config showIn the desktop app
Section titled “In the desktop app”Who can read new sessions sits on the setup wizard’s agents page, Connect kcap to your harnesses, below the agent list. Neither Continue nor Not now works until you pick one. The workspace decides which choices appear: People I share a project with only on Team and Enterprise, and the organisation choice only when the workspace names the organisation’s repository owners, which then appear in its label. Your pick is saved to your active profile as default_visibility, the same setting kcap config set default_visibility writes, so the last one written wins

After setup, change it in Settings → Privacy under Who can read new sessions, which applies to the profile the app runs against. The choices are the ones your workspace offers, as in setup; nothing is saved until you press Save, and sessions already on the server keep their audience. It sets the audience a session starts with; Share on a single session in the web app overrides it for that session

History imported during setup takes the same default: on the wizard’s next page, Bring your history with you, a repository ticked for import is shared with that audience unless you also tick its Only me box under Customize, which imports it private. Keep private repos out covers that page
On the local edition the wizard and Settings → Privacy leave out Who can read new sessions, and the setting is private: sessions are always yours alone
Admins set which repository owners count as the organisation’s under Administration → General → Sessions
One session
Section titled “One session”In the web app, open the session from Sessions and choose Share in its header. The audiences offered depend on your plan and the repository’s projects:
- My default: inherit whatever your default was
- Org members: everyone in the organisation, as a deliberate choice that survives a change to your default
- Project members: members of the projects holding this repository; adding the repository to another project widens it
- Teams & people: only the teams and people you pick. Admins create native teams; a team grant follows the team’s membership, so adding someone to the team gives them every session shared with it
- Private: only you
Choose, add recipients if needed, and Apply. If the server is catching up, the change is saved and shows once it is done. A continuation chain is several sessions; share each segment that matters
Sharing a session is a web app control. The desktop app has none, and your agent has no tool for it
A hosted agent’s page has its own sharing control, which shares the agent; viewers open it only if they can also read its session. When they cannot, the page says who is left out and offers Share the session with them or Keep it private


How much they see
Section titled “How much they see”Where the Detail level selector is offered: Full includes the transcript and tool output; Activity shows what happened without the conversation; Overview shows the outcome and metadata. You always have full access to your own sessions. The same limits apply to what an agent can read through kcap’s tools on the reader’s behalf
What never grants access
Section titled “What never grants access”A link. Knowing a session id. Being in the same repository. If someone outside the audience opens a session link they see “not available”, the same as for a wrong link
Further reading
Section titled “Further reading”- Hide a session narrows one to owner-only in a single step
- Keep private repos out decides what is stored at all