Settings

Press s from the task list to open the Settings screen.

Dates are displayed using your system locale and timezone — no configuration needed.

Settings file

Settings are stored in ~/.tide/settings.json. You can edit this file directly — changes take effect on the next poll cycle.

Atomic writes

Tide writes settings atomically (temp-then-rename). Avoid holding the file open while Tide is running.

Profiles

Profiles live in settings.json under profiles — a map of profile names to their config. Each profile declares which agent to use and, optionally, how to authenticate. Task frontmatter references a profile by name.

The onboarding screen sets up minimal profiles on first launch. To add, edit, or remove profiles later, edit ~/.tide/settings.json directly — changes take effect on the next run.

{
  "profiles": {
    "my-claude": {
      "agent": "claude-code"
    },
    "my-copilot": {
      "agent": "copilot"
    }
  }
}

# in task frontmatter
profile: my-claude

Profile fields

Field	Description
agent	Which agent plugin to use. See Agents below.
model	Optional model override. Format depends on the agent (e.g. Bedrock ARN for claude-code, model name for gemini).
auth	Optional auth config. Shape depends on auth.type. See Auth types below.
env	Optional environment variables injected at runtime into every task that uses this profile. Task-level env takes precedence. Changes take effect on the next run — no sync required.

{
  "profiles": {
    "my-claude": {
      "agent": "claude-code",
      "env": {
        "CLAUDE_BIN": "claude"
      }
    }
  }
}

Agents

Runs Claude Code via the @anthropic-ai/claude-agent-sdk. No auth block is needed for local use — authenticate once with claude /login or set ANTHROPIC_API_KEY, and Tide picks up those credentials automatically.

{
  "profiles": {
    "my-claude": {
      "agent": "claude-code"
    }
  }
}

An auth block is only required when credentials must be injected at run time (e.g. AWS Bedrock via Teleport — see tsh below).

{
  "profiles": {
    "my-claude-bedrock": {
      "agent": "claude-code",
      "model": "arn:aws:bedrock:eu-central-1:...",
      "auth": {
        "type": "tsh",
        "auth": "okta",
        "app": "my-tsh-app",
        "awsRole": "bedrock-developer-user",
        "teleportProxy": "teleport.example.com:443"
      }
    }
  }
}

Auth types

The auth block in a profile is optional. When present, auth.type determines how credentials are obtained before the agent runs.

tsh

Wraps agent execution in tsh aws to inject temporary AWS credentials and a proxy into the environment. Use this when your model is hosted on AWS Bedrock and access is brokered via Teleport.

Field	Description
type	tsh
auth	Auth provider passed to tsh aws --auth (e.g. okta).
app	Teleport application name passed to tsh aws --app.
awsRole	AWS role passed to tsh aws --aws-role.
teleportProxy	Teleport proxy address passed to tsh aws --proxy.

tsh injects AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and HTTPS_PROXY into the agent process environment. The agent-runner validates these are present before starting the run.