Board Profiles

A Board Profile is a named alternate ladder of per-column strategy settings. One task can run Planning in Opus at xhigh and Merge in Sonnet at high while another task rides a cheaper ladder over the same board. Column identity - which columns exist, their names, order, roles, colors, and icons - stays singular; a profile scopes only the strategy: agent, model, effort, permission mode, auto-command and its timing, auto-spawn, handoff, session target, spawn strategy, and plan-exit target.

Creating and Editing Profiles

Profiles are authored in Edit Columns. The column rail carries a Profile switcher at its head: Default, or any named profile, with contextual actions - New, Duplicate, Rename, and Delete (Default offers only New). Selecting a profile switches every column editor below to that profile’s values.

While a profile is selected, column structure is locked - no adding, reordering, or deleting columns. Structure belongs to the board itself; a profile only changes what each column does to a session.

A profile entry is sparse, with three states per field:

State	Meaning
Field absent	Inherit the column’s own setting
Field explicitly cleared	Use the agent default, even where the column pins a value
Field set	Use the profile’s value

Riding a Profile on a Task

The New Task and task-edit dialogs ask How this task runs with two mutually exclusive cards:

• Column Settings - each column applies its own settings as the task moves. This card holds a Profile dropdown: Default, or any named Board Profile. The dropdown is disabled until the board has at least one profile, so the concept stays discoverable without a second creation path (profiles are created in Edit Columns).
• Agent Override - agent, model, effort, and permission mode pinned for the whole task, ignoring column settings. An edit pencil beside the Agent field jumps to Settings > Agent for the project’s defaults.

Picking one card clears the other - a task never carries both a profile and override pins. The choice persists with the task, and the running session’s context bar shows a profile pill you can switch mid-task, alongside the model and effort pickers.

Sharing Through kangentic.json

Profiles live in the team-shared kangentic.json, never in kangentic.local.json - a task’s saved profile choice must resolve on every teammate’s machine. Within a profile, column entries reference columns so that copying a profile between projects with the same column names works, and the plan-exit target is stored by column name for the same reason.

Editing a profile propagates live: running sessions in affected columns pick up the new ladder the same way direct column edits do. Deleting a column through Edit Columns or MCP also prunes it from every profile; editing kangentic.json by hand does not prune, so a hand-removed column can leave dangling profile entries until the next in-app edit.

Note

Profiles ride the same resolution chain as everything else: a task’s Agent Override beats a profile, a profile beats the column’s own settings, and the column beats project defaults.

Agents Manage Profiles Too

The MCP server exposes profiles to running agents: kangentic_list_board_profiles, kangentic_create_board_profile, kangentic_update_board_profile, and kangentic_delete_board_profile, plus a profile parameter on kangentic_create_task and kangentic_update_task - so a planning agent can set up a cheap review ladder and file tasks that ride it, without you opening Edit Columns.

Next steps

Next: Board Configuration - the kangentic.json file profiles live in.

See also:

• Custom Workflows - the per-column settings a profile overlays
• Creating Tasks - the How this task runs choice on every task
• MCP Server - the board-profile tools