Project configuration
Vitrino runs Claude Code unchanged, and that includes configuration. Everything your project and user setup already define is read as it always was — there is no Vitrino‑specific config file, and nothing to port.
Instructions
CLAUDE.md files are loaded exactly as Claude Code loads them: the managed, user, project and local files, concatenated in that order, with @path imports followed. AGENTS.md is read where there is no CLAUDE.md.
So opening a repository in Vitrino gives Claude the same instructions it would have in a terminal, from the same files.
Topic rules under .claude/rules/ and auto memory work the same way.
The .claude directory
Both the project's .claude/ and your ~/.claude/ are read: settings, hooks, skills, commands, agents, rules, output styles and memory.
Vitrino does not write to them, with one exception — Always allow on a permission card saves a rule, and the card tells you which file it will be written to before you press it. See Permissions.
Settings and precedence
Claude Code's precedence applies: managed, then project local, then shared project, then user, with lists merged across scopes.
Vitrino's own settings — your API key, notifications, what the transcript expands — are separate and live in Vitrino's application data folder. They do not affect Claude's behaviour.
Permission rules
Rules in your settings files are honoured, so what you have already allowed stays allowed and you are not asked again. A rule that denies something is honoured too: Claude is refused without a card appearing.
Authentication is the exception
This is the one place Vitrino deliberately does not follow your environment.
Claude Code picks a credential from a chain of environment variables and files. Vitrino clears all of them and passes only the credential chosen in Settings → Account.
The reason is that inheritance is unpredictable for a desktop app: launched from the Dock or Start menu it sees none of your shell, launched from a terminal it sees all of it. The same app would bill two different ways depending on how it was opened. An explicit choice is the only honest option. See First run.
MCP servers
Read from your Claude Code configuration. See MCP servers.
Claude Code's own documentation
For what any of these files can contain, read the source: