Deleting a project
Deleting a session deletes its project: its messages, plans, code, previews, scenario cases and the traces your application sent for it. Files you uploaded stay in Files until you delete them there. The session’s creator, or a workspace owner or admin, can delete it.
Access ends at once
Section titled “Access ends at once”The moment you delete, nobody in the workspace can open the session, read its code or files, or query its traces, through the web app, the API or MCP. Its running work stops and its ingest keys stop accepting traces.
The data is then purged, and the purge is recorded
Section titled “The data is then purged, and the purge is recorded”A purge removes the data everywhere WeHarness keeps it:
- running sandboxes are ended;
- the traces are deleted from the trace store;
- messages, runs and model and decision content are removed from the database;
- knowledge kept only for an uploaded repository, such as memory, lessons and scenario cases, is removed too.
WeHarness records what each kind of data lost, so the deletion can be checked. Usage numbers stay, without content, so credits and costs still reconcile.
A restore cannot bring it back
Section titled “A restore cannot bring it back”Every deletion also leaves a tombstone in object storage, outside the database. If the database is ever restored from a backup taken before the deletion, WeHarness applies every tombstone again before it serves anyone, hides the project again and purges it again.
What cannot be recalled
Section titled “What cannot be recalled”Content already sent to a model provider, or copied outside WeHarness (for example a pull request already pushed to GitHub), is not recalled by deleting the project in WeHarness.