Profile

A profile configures an Agent node's provider, model, reasoning effort, and additional provider arguments. The node selects it independently of its session, which controls conversation continuity. One profile may serve several independent sessions.

Countdown example

The decrement Agent node selects the decrementer profile parameter. The workflow binds that parameter to the invoker that proposes the next integer. The separately selected countdown session determines whether successive proposals share a provider conversation.

Scope

A profile ID denotes a role, such as decrementer or planner. The selected provider and options belong to the concrete profile configuration, so a caller can bind the same parameter to different configurations.

The options object holds model, reasoning_effort, and extra_args. Provider-specific settings belong in extra_args, with one list item per command-line argument. For example:

Provider	extra_args	Effect
Codex	["-c", "web_search=\"live\""]	Request live web search.
Codex	["-c", "web_search=\"disabled\""]	Disable the web search tool.
Claude	["--tools", "Read,Glob,Grep,WebSearch,WebFetch"]	Select file-reading and web tools.

See the Codex configuration reference and Claude CLI reference for provider options. Codex uses its configured defaults when no override is supplied. Read-only Claude requests default to Read,Glob,Grep; an explicit --tools list may select those tools and WebSearch,WebFetch. Editing and command-execution tools remain unavailable in read-only requests. Additional arguments cannot override runtime-managed flags for workspace access, output collection, or session handling.

Profiles are either local or parameters:

Kind	Configuration
Local profile	The subroutine owns a generated invoker configured by its profile declaration.
Profile parameter	A workflow entry or subroutine call maps the parameter to a profile in the caller's resource scope.

Authored files

Profiles have no authored files. Configuration changes modify the project declaration and regenerate the affected modules.

Files

General profile structure

profiles/
├── ◆ __init__.py
├── <local-profile>/
│   └── ◆ __init__.py
└── <profile-parameter>/
    └── ◆ __init__.py

File	Role
◆ profiles/__init__.py	Collects local profiles in PROFILES and profile parameters in PROFILE_PARAMETERS.
◆ profiles/<profile>/__init__.py	Declares either a local PROFILE or a caller-supplied PROFILE_PARAMETER.

These paths are relative to a subroutine. A workflow owns concrete profiles in the corresponding directories, with its declarations and registry described under Workflow: Profile declarations and registry.

Generated files

See the generated declaration reference for the Python declarations and registries maintained by generation.