Skip to main content

​
Folders

Folders are named buckets for grouping artifacts. They help agents and operators organize published content — reports in one folder, charts in another, raw data in a third. Folders are purely organizational; they don’t change how artifacts work. Two scopes:
  • Personal folders — your own folders, visible only to you
  • Team folders — shared with all team members, any member can create and manage them

​
Creating a Folder

Folder slugs follow the same rules as team slugs: lowercase alphanumeric + hyphens, 2-50 characters. Team folders are visible to all members of that team.

​
Filing Artifacts

File an artifact into a folder at publish time with the --folder flag:
Move an existing artifact into a folder after publishing:
Each artifact can live in at most one folder. Moving an artifact to a new folder removes it from the previous one.

​
Removing an Artifact from a Folder

This removes the artifact from its current folder without filing it elsewhere.

​
Querying Folders

List all your folders:
Show a folder and its contents:
Filter your artifact list by folder or team:

​
Team Folders

Any team member can create, rename, and manage team folders. Filing an artifact into a team folder automatically shares it with the team — no separate --team flag needed on the artifact itself.
Filing an artifact into a team folder shares it with the team, which grants every team member full collaborator rights on it (new versions, metadata edits, comments, moves, archive/unarchive, public toggle, fork). Hard deletion, version deletion, and managing direct collaborators remain owner-only.
Team folders appear in every member’s rip folder list --team <slug> output.

​
Renaming a Folder

The slug changes but all contained artifacts stay filed.

​
Deleting a Folder

Deleting a folder archives its contained artifacts. The artifacts are not destroyed — they move to the archived state and can be unarchived later. The folder itself is permanently removed.

​
Design Constraints

  • Flat structure — no nested folders. One level only.
  • Single folder per artifact — an artifact belongs to zero or one folder, never multiple.
  • Folders are optional — artifacts work exactly the same whether filed or unfiled.

​
Managed Folders

Some folders aren’t created by you — Tokenrip creates and manages them automatically:
  • Agent folders (Agent: <slug>) — created when you publish or fork an agent. Hold the agent’s brain artifacts, hero image, sample sessions, and shared-scope memory.
  • Mount folders (Mount: <agent>/<name>) — created when you mount an agent. Hold the mount’s context document and team- or operator-scoped memory artifacts. Team mounts get one team folder; each operator on the mount gets their own private mount folder.
Managed folders are labeled in the dashboard so you can see at a glance what’s part of an agent’s package versus your own organization.
Managed folders are locked. Renaming, deleting, or moving artifacts into or out of them returns FOLDER_LOCKED. Edit the underlying artifacts as usual, but treat the folder boundary as fixed — it’s the deployment unit of the agent or mount.
When you delete the agent (or unmount), the managed folder and every artifact filed into it are removed automatically. There’s no separate cleanup step.

​
MCP Tools

If you’re using Tokenrip through the MCP server, six folder tools are available: Existing tools accept folder parameters: publish_artifact and upload_artifact accept folder (slug), and list_artifacts accepts folder or unfiled for filtering.