The .rusty folder · Rusty IDE

Rusty keeps a project's data in a .rusty/ folder at the root of the workspace. Most of it is plain JSON you can read, diff and share.

your-project/
└── .rusty/
    ├── profiles/        behavior profiles       (commit)
    ├── workflows/       workflow definitions    (commit)
    ├── skills/          your skills             (commit)
    ├── canvas/          Rusty Canvas documents  (your call)
    ├── chats/           Agent Mode conversations (your call)
    ├── observability/   tool execution records  (git-ignored automatically)
    └── metrics/         token usage             (git-ignored automatically)

What each folder holds

Folder	Contents
`profiles/`	One JSON file per behavior profile: `<id>.json`. See Profiles & workflows.
`workflows/`	One JSON file per workflow: `<id>.json`. The built-in workflows are part of the app and are not stored here; only workflows you write or customize are.
`skills/`	One JSON file per skill you create: `<id>.json`. See Skills.
`canvas/`	Saved Rusty Canvas documents: the graph, node logs and status, and the virtual workspace contents.
`chats/`	One file per Agent Mode conversation, with its messages and the files it modified.
`observability/`	Local records of tool executions, diagnostics and run trajectories. See Observability & metrics.
`metrics/`	Token usage events and summaries for Token Metrics.

What to commit

Share the files that define how agents behave so your whole team gets the same setup:

.rusty/profiles/
.rusty/workflows/
.rusty/skills/

Rusty writes a .gitignore containing * inside observability/ and metrics/, so those stay out of version control without any setup.

Chats and canvases are personal working state and can be large. Whether to commit them is up to you; add .rusty/chats/ and .rusty/canvas/ to your .gitignore if you would rather not.

What is not stored here

Provider API keys and MCP server credentials are not in .rusty/. They live in Rusty's encrypted application configuration. See Data, storage & privacy.

Editing files by hand

Profiles and workflows are ordinary JSON, and the Behaviors editor keeps any fields it does not know about, so hand edits and editor edits coexist. A file with validation problems is flagged in the editor.