The trash
Nothing is deleted on your machine. Everything is moved, with a receipt, and one press brings it back for thirty days.
One rule, every screen and every route: a delete moves something to the trash.
It does not remove it.
What that means
Delete a chat, a skill page, a role, a task — any of them — and it goes
into .beafk/trash inside the project it belonged to, with a receipt saying what
it was and when it went. It stays there for thirty days.
One press puts it back.
Where the trash is
settings → trash, on the machine's panel. Everything that has been deleted,
newest first, with what it was and where it came from.
It is in settings rather than on the home screen — a drawer of the machine's,
not a place work is done.
The row goes immediately
When you delete something, it disappears from the screen at once, before the
machine has finished answering. "I deleted it and it is still there" is the bug
that rule exists to prevent.
What is thrown away instead
Only things the machine can make again: a cached transcript, a note that a
chat was live, a published copy of a skill in an agent's folder, a
pointer to a chat that has itself gone to the trash. Bookkeeping, not
content.
The one exception
A set of variables is forgotten rather than trashed. The trash is a folder
inside a repository, and moving a live credential into one is the opposite of
what you asked for. Deleting secrets deletes them.
After thirty days
It goes. If you want something kept, take it out of the trash before then.
What this does not cover
Anything an agent did to your files. A file an agent deleted from your
repository comes back from git; the trash is for the things beafk itself owns.
Most of what ends up in here is deleted from a thread — see
a chat.