Delete a session

Deleting a session stops any further storing of it and removes its data from the server, including its subagents. It cannot be undone

From your agent

Stop storing this session and delete it

The disable skill does both

From the terminal

kcap disable                 # the session this terminal is in
kcap disable <sessionId>     # by UUID

The command stops the local watcher, silences future capture for that session, and asks the server to delete it. No confirmation is asked. Read the result: if the server could not be reached, local storing is off but the server copy remains; retry when you are connected

What stays behind

• The agent’s own transcript file on your machine. kcap never writes to it and never deletes it
• Other segments of a continuation chain, unless you delete them too
• Anything already derived and anonymous, such as counts in Insights, is recomputed as the projections catch up

Deleting imported history

kcap disable <id> works on imported sessions too. To keep history off the server in the first place, scope the import with --repo or --cwd, or exclude the folders before importing. --private does not keep anything off the server: it uploads the sessions readable by you alone

Deleting everything

Your own data as a member: delete sessions individually, or ask an admin. An organisation’s data: see Data security and privacy. A local edition: kcap local uninstall --purge removes the server, its data and its logs from the machine