Session configuration in TUI and web

Both interfaces use the same React components, controller APIs and ownership checks.

Session Settings

Open Sessions → Settings (or press Shift+P in the focused Sessions list) and navigate Project → repository → agent → session. A separate Global defaults branch contains the operator's Claude and Codex defaults. ↑/↓ moves between entries at the focused level; → expands a branch and enters its first child, ← collapses or returns to the parent, and Esc returns to the parent. At the root, Esc returns focus to the sidebar. Tab returns directly to the sidebar. Browser clicks use the same navigation and editing callbacks.

On Claude or Codex, Enter/e opens the typed defaults editor. On an agent with sessions, → opens its session list. Selecting a session identifies the exact conversation for R; it does not introduce a session-specific template scope. The editor explicitly states that saving changes the repository's defaults for that agent. A session from another repository sharing the same container is grouped under its actual repository, not the container owner's repository.

The existing layers remain unchanged: global manual defaults, the repository's tracked .devctl.yaml declaration, its local manual overrides, and the immutable snapshot captured by a session. x removes one local override, s saves defaults without restarting anything, and R offers a settings restart of the selected session. Y confirms native resume; if no native session identity exists, a new conversation needs separate C confirmation. Other sessions keep running. Active autonomous runs retain their existing reconfiguration requirements.

Server users can view effective global defaults and edit only their own repositories. Global edits belong to the infrastructure operator. Other CLI providers are visible under their repositories but use native client configuration; devctrl does not offer unsupported typed fields or pretend those clients have managed settings snapshots.

Session Launch Profiles

A launch profile is an optional saved recipe for new sessions. It selects an agent, account policy, Agent Packs, required services, declared forwards and placement requirements. It does not control the provider's model/reasoning settings; those belong to Session Settings. Normal session creation does not automatically create a profile, so a fresh installation initially has no profiles.

Browser profiles use a grouped project/repository list and labeled form controls; the console menu stays visible while editing. Native forms retain their keyboard workflow.

Open Launch Profiles, choose a repository and use Create launch profile (n). The empty state always includes a creation entry under each repository. e edits a manual profile, c makes a copy, d requests deletion and Y confirms it. Editing a tracked .devctl.yaml profile creates a manual copy; the UI does not overwrite a declaration that synchronization would restore. Deleting a recipe does not stop or delete its sessions or containers.

l / Start with profile opens the existing launch wizard with that exact profile selected, including when it is not the first profile alphabetically. The normal host, container, history, account, policy and folder steps remain available. Account policies are project-default, work-first, any-logged-in or an explicit owned account. Existing quota and authorization checks still apply.

Agent Pack IDs and service IDs are selected from available controller metadata; forward names must already be declared for the repository. A profile grants no services, credentials, network access or filesystem access. The launch API checks required service grants and configured forwards before accepting the session. CPU and RAM values are host placement requirements used by recommendations; saving or applying a profile does not change limits on an already-running shared container. Unexposed resource metadata is retained during edits and copies.

Profiles currently participate in the managed Claude/Codex launch workflow. Other client providers remain configured through their native client support. Profile CRUD is owner-scoped: a server user cannot overwrite another user's profile ID or attach foreign credentials or ungranted integrations.

The existing .devctl.yaml, CLI launch-profile and session MCP settings tools remain compatible. Agent sessions use get_session_settings, apply_session_settings and clear_session_settings only for their own repository/provider scope. No new agent-side permission bypass is introduced by the navigation changes.

Operator CLI profile operations are launch-profile list PROJECT, launch-profile put --file PROFILE_JSON and launch-profile delete PROFILE_ID. HTTP reads use GET /v1/projects/:id/launch-profiles or the scoped sessionLaunchProfiles snapshot; writes use POST /v1/session-launch-profiles and DELETE /v1/session-launch-profiles/:id. TUI/web use the same typed records and controller ownership checks.

Browsing configuration

The Settings view inside Sessions opens a Project → repository → agent → session tree in both TUI and web. Its selected scope, utility actions and keyboard hints stay at the bottom of the native working area. From a selected session, Settings reveals that exact conversation in its repository branch. Press l to return to the Sessions list; s on a session still opens its exact typed editor directly. Legacy /session-settings links open the same view. Select a row to see its scope and summary, expand a branch to navigate, and edit the exact agent defaults or session. Web presents selected overrides as labeled fields instead of a combined inheritance paragraph. Native navigation and its bounded viewport stay active at the current tree level.