Templates

tmux-ide init --template <name> copies a shipped template into .tmux-ide/workspace.yml, replaces its example name with the current project directory, validates it as WorkspaceConfigV1, and then writes it.

Shipped names

Run, for example:

tmux-ide init --template nextjs
tmux-ide validate --json
tmux-ide start

Representative generated file

The shipped default template currently produces this structure (the name is rewritten for your directory):

name: my-project
version: 1

terminal:
  rows:
    - size: 70%
      panes:
        - id: agent-1
          title: Claude 1
          command: claude
        - id: agent-2
          title: Claude 2
          command: claude
    - panes:
        - id: changes
          title: Changes
          type: changes
        - id: dev
          title: Dev Server
        - id: shell
          title: Shell
          focus: true

Stable pane id values are included so the daemon can preserve semantic identity independently of display titles.

Additional team scaffolding

The agent-team, agent-team-nextjs, and agent-team-monorepo templates also copy the bundled skill files and create, when missing:

• .tmux-ide/library/architecture.md
• .tmux-ide/library/learnings.md
• .tasks/validation-contract.md
• AGENTS.md

The missions template creates the same files plus .tmux-ide/skills/. Existing files are not overwritten.

These templates create agent-ready pane layouts and project context. They do not add a legacy orchestrator block or automatically dispatch work. See Workspace layouts for the current declarative agent and mission fields.

Automatic detection

Without --template, tmux-ide init detects the stack. Recognized frameworks produce a suggested layout; otherwise it falls back to default:

tmux-ide detect --json
tmux-ide init

Use tmux-ide detect --write when you want detection to write directly. Both commands refuse to overwrite an existing workspace config.