Project config files

What Tegment stores in your repo's .tegment/ folder — and what it doesn't.

Tegment keeps a small amount of shared, per-project configuration in a .tegment/ folder inside the repository. These files are meant to be committed, so everyone who opens the project in Tegment gets the same setup. Everything else — your account, theme, keyboard shortcuts, and your GitHub/Jira credentials — is stored privately on your machine, not here.

You set all of this up through Tegment's UI — this page documents the on-disk format so you can review or version-control it, not because you have to edit it by hand. The folder is created the first time you save one of these configs; an empty repo won't have a .tegment/ until then.

.tegment/config.json#

Holds the commands tied to a project. See Quick actions for the full field reference.

{
  "postCreationCommands": [
    { "name": "Install", "command": "npm install", "continueOnError": false, "order": 0 }
  ],
  "templates": [
    { "name": "Dev server", "command": "npm run dev", "runMode": "visible", "order": 0 }
  ]
}

.tegment/launch.config#

Holds your build & run configs.

{
  "buildRunConfigs": [
    { "id": "web", "name": "Web app", "runCommand": "npm run dev", "order": 0 }
  ]
}

.tegment/reviews/#

Where AI review saves its reviews, one Markdown file per ticket and reviewed commit. Unlike the files above, this folder is not meant to be committed: Tegment adds it to the repository's .git/info/exclude, so it stays in your clone and out of your changes.

.worktreeinclude#

Not part of .tegment/, but read by Tegment too: a file at the repository root, in .gitignore syntax, listing the gitignored files to copy into every new worktree, such as .env. Claude Code reads the same file. See Worktrees.

What lives outside .tegment/#

These are not in the repo — they're app settings on your machine, set through the UI:

• Project list and worktree location — where each project lives and, optionally, a custom folder for its worktrees.
• Theme and appearance — chosen in the app, not the repo.
• Keyboard shortcuts, terminal shell/font/scrollback — see Terminals.
• Quick actions — the agent-launch commands for tickets; see Quick actions.
• GitHub and Jira connections, including tokens, which are stored encrypted. Per-repository issue sections live here too.