# Data mode switch, tokens in the dashboard and plans from Claude Code

> 2026-10-19 · CLI 0.4.1 · New, Improved, Security, Dashboard · https://comity.so/changelog/2026-10-19-data-mode-tokens-and-plans

Owners can now switch what code details Comity keeps, owners and admins can create tokens for CI right in the dashboard, and when you approve a plan in Claude Code, Comity records it with your work.

## New

### Switch the data mode

Owners pick **Full** or **Metadata only** in **Settings → Organization** and click **Save data mode**. Switching to Metadata only applies at once: signature text Comity already stored for your org is cleared, and only hashes are kept, so conflict detection keeps working. Each change is recorded in the audit log. Ask your team to run `comity login` again so their CLI picks up the new mode. See [Data modes](/docs/admin/security#data-modes).

### Create tokens in the dashboard

Owners and admins click **Create token** in **Team → Tokens**. Pick a **service token** for CI and bots (never billed) or a personal token, a preset (**CI / GitHub Actions** or **Full agent**) and an optional expiry. The token is shown once, with a copy button and a ready-to-paste GitHub Actions step that fails the build on blocking conflicts.

### Plans from Claude Code's plan mode

When you approve a plan in Claude Code, it becomes the plan of your session's intent (Comity drafts an intent if there isn't one yet), next to its title, scope and claims. Run `comity init` again (and commit the change) to add the new hook; `comity doctor` tells you when it's missing. See [What happens on each event](/docs/how-it-works#what-happens-on-each-event).

## Improved

- Override reasons can be made optional: set [`override.require_reason`](/docs/admin/policies#override) to `false`. It stays required by default.

## Changed

- Protected-path owners are people: each owner must be `user:<email>`. Other prefixes, such as `team:`, are rejected when you save the policy. See [protected_paths](/docs/admin/policies#protected_paths).