The cross-provider example only had worker profiles with provider
overrides but no supervisor profile showing how to use them. Added
cross_provider_supervisor.md and updated README with installation
and usage instructions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Add report_generator_codex.md with codex provider override
- Update cross_provider_supervisor.md to use report_generator_codex
  for the handoff step, demonstrating 4 providers in one workflow
  (Claude Code, Gemini CLI, Kiro CLI for assign + Codex for handoff)
- Update README with the new profile and installation step

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…cription

- Update README cross-provider section: add kimi_cli and copilot_cli
  to the valid provider values list
- Fix cross_provider_supervisor.md description to include Codex

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Add data_analyst_codex.md and data_analyst_copilot_cli.md for full
  provider coverage
- Rewrite cross_provider_supervisor.md to make clear you pick the
  worker profiles matching your installed providers — not all required
- Split README profiles table into Supervisor / Data Analysts / Report
  Generator sections with guidance on selecting the right ones
- Show commented-out install lines so users can uncomment what they need

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…uide

Supervisor now references claude_code, gemini_cli, and kiro_cli by
default (plus report_generator_codex for handoff). README explains how
to customize the supervisor to use other providers like codex or
copilot_cli, and how to create your own cross-provider profiles.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Match the structure of examples/assign/README.md: add cao-server start
step, numbered setup instructions, all provider launch variants, and
the example task prompt for the supervisor terminal.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…URLs

Restructure the Web UI section into Option A (dev mode) and Option B
(production mode) with explicit "open browser" instructions for each.
Remove duplicated build section. Move remote/SSH instructions to the end.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

cao install copies profiles to ~/.aws/cli-agent-orchestrator/agent-context/
but this directory was not scanned by agent_profiles.py or shown in the
Web UI settings. Add it as 'cao_installed' in the default agent directories
so installed profiles are discoverable.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…ssions

When CAO spawns Claude Code in tmux, it strips all CLAUDE* env vars to
prevent "nested session" errors. This also removes CLAUDE_CODE_USE_BEDROCK,
which is required for Bedrock authentication, causing Claude Code to show
"Not logged in". Preserve this specific var in both tmux.py (env filter)
and claude_code.py (shell unset command).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…Bedrock

The env var is needed for all authentication modes (Bedrock, custom
models, and default Claude Code credentials), not just Bedrock.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Users who installed via `uv tool install` don't have the web/ directory.
Added a note with clone instructions at the top of the Web UI section.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…uth env vars

- web/README.md: frontend architecture, tech stack, components, data flow
- docs/settings.md: agent directory configuration, settings.json format, API
- README.md: link to new docs, clarify Web UI requires cloned repo
- CHANGELOG.md: update v2.0.0 release date to 2026-03-28
- tmux.py + claude_code.py: preserve all CLAUDE_CODE_USE_* and
  CLAUDE_CODE_SKIP_*_AUTH env vars (Bedrock, Vertex AI, Foundry)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>