Erase data

Owners and admins erase Sessions, conversations and any Chat message. Every member erases Organization memory entries and the Chat messages they wrote. Erase data lists what an erasure removes and what stays.

Erase a Session

An owner or admin can erase a Session with everything devboxes stored for it:

{ "organizationId": "<organization id>", "sessionId": "<session id>" }

devboxes invoke sessions.erase --input @session.json

Stop the task first. Branches, pull requests, and comments in your repository stay.

Erase an Organization memory entry

Find the entry's index with memory.list, then erase it:

{ "organizationId": "<organization id>", "index": 12 }

devboxes invoke memory.erase --input @entry.json

The entry's text is gone. Its index, author, source and date stay.

Erase Chat messages

In the thread, ask devboxes to forget what was said, for example "Forget the access code I posted." It erases those messages and says what it erased.

From the CLI, find the messages' id with chat.zoom, opening a line with n 1 to see a message whole, then erase the ones you wrote with chat.erase-own-messages. An owner or admin erases anyone's with chat.erase-messages:

{ "organizationId": "<organization id>", "conversationId": "<conversation id>", "ids": [4, 5] }

devboxes invoke chat.erase-own-messages --input @messages.json

The answer lists the messages it erased and the Organization memory entries that those messages saved, which are erased with them. A message stays while devboxes still needs it for a reply it hasn't posted, so erase it again once the reply is in the thread. Erasing doesn't delete the posts in your chat app: delete your own there.

Erase a Chat conversation

Erasing a conversation leaves the Sessions in which it started work, and Chat stops showing them. To remove that work too, erase it first, while you can still find it:

1. Run chat.inspect-conversation. Note its sessionIds and the externalMessageId of its turns. sessionIds lists every Session that is not erased and in which the conversation started work: the Sessions it started and the Sessions it continued, including Sessions in Projects that its channel no longer uses.
2. Check the Sessions with sessions.inspect before you erase them. A Session that the conversation continued can also hold work that someone else started from the CLI, the API, or another thread, and sessions.erase removes all of it. Erase the Sessions that you want to remove with sessions.erase.
3. Run memory.list. Erase the entries whose source names one of those Sessions or message IDs with memory.erase.
4. Erase the conversation with chat.close-conversation and "erase": true.

A direct conversation in a chat app starts no Sessions and adds no Organization memory entries, so you can erase it without these steps. Only its Person can inspect it. Your own web conversation can start Sessions, so these steps apply to it. You can close or erase the conversation yourself, but erasing its Sessions with sessions.erase still needs an owner or admin.

Have a Person or a Persona removed

You delete one of your own preferences with people.forget, or by asking devboxes in your direct message. No command erases a Person or a Persona. To have them removed, write to [email protected].