Skip to content

Saved assistant conversations

Conversations with the Host assistant are saved to your history in the Organization where you had them, so you can come back to them. This page is the privacy statement for that history and the reference for the routes behind it.

For every turn the assistant panel showed, Canopy keeps:

  • the question and the answer, as text;
  • the context references the turn carried (an environment, a build, a commit and the labels the panel showed for them);
  • the records the answer retrieved, its grounding, and the limitations it stated;
  • the model name and the token count.

Canopy never stores secret values. The assistant is never given them, and a message that contains what looks like a credential (a private key, a bearer token, a JWT, or a GitHub, GitLab, OpenAI, AWS or Canopy API key) is refused with 422 secret_in_content instead of being saved.

Only you. A saved conversation belongs to your account in one Organization. Teammates, Organization owners and admins cannot list, read, export or delete it, and nothing is shared. A request for someone else’s conversation answers 404, the same as for one that does not exist.

A conversation is deleted automatically 180 days after its last activity. Adding a message restarts the period. The API shows the date as expires_at. A daily job deletes expired conversations and their messages.

You can delete sooner at any time, and the deletion is permanent:

  • one conversation, or all of yours in an Organization, through the API or SDK below;
  • all of them at once by leaving the Organization: removing a member deletes that member’s conversations in it;
  • deleting the Organization deletes everything saved in it;
  • deleting your account deletes everything you saved, in every Organization.

GET /account/gdpr/export includes assistant_conversations: every conversation you saved, across Organizations, with all of its messages and the evidence each turn carried. A single conversation can be exported on its own.

All routes are under /teams/{team_id}/assistant/conversations and need an Organization membership of any role. They only ever act on the caller’s own conversations.

Route Purpose
GET / List yours, newest activity first. limit defaults to 50, at most 100; pass next_cursor as cursor for the next page.
POST / Save a conversation: title (at most 200 characters), optional focus_ref, optional messages.
DELETE / Delete all of yours in this Organization. Returns { "deleted": n }.
GET /{id} Read one with its messages.
DELETE /{id} Delete one.
POST /{id}/messages Append 1 to 10 messages.
GET /{id}/export The same content as a JSON download.

A message has role (user or assistant), content (at most 20000 characters) and optionally context, retrieved, grounding, limitations, model and total_tokens. Each JSON field may be at most 64 KiB.

Limits: 200 conversations per person per Organization (409 conversation_limit), 500 messages per conversation (409 message_limit), and 60 writes a minute.

const saved = await sdk.spaces.createAssistantConversation(teamId, {
title: "Why did production return 502?",
messages: [{ role: "user", content: "Why did production return 502?" }],
});
await sdk.spaces.appendAssistantMessages(teamId, saved.id, [
{ role: "assistant", content: "The last deploy failed its health check.", limitations: ["Logs were not read."] },
]);
const page = await sdk.spaces.listAssistantConversations(teamId, { limit: 20 });
await sdk.spaces.deleteAssistantConversation(teamId, saved.id);