Skip to content

Workboard hardcodes Codex execution metadata for Claude agent runs #108362

Description

@buhrclaw

Summary

Workboard records every dispatched agent session as engine: codex, model: default, and an execution id ending in :codex, even when the assigned agent actually runs through Anthropic Claude CLI with Claude Opus.

Root cause

extensions/workboard/src/dispatcher.ts hardcodes the execution metadata in buildExecution:

id: params.card.execution?.id ?? `${params.card.id}:codex`,
engine: "codex",
model: params.model,

DEFAULT_DISPATCH_MODEL is default. Meanwhile subagent.run receives an agent-scoped session key and no explicit provider/model, so the actual run correctly inherits the assigned agent's configured runtime.

Observed result:

  • Workboard execution: engine=codex, model=default
  • Actual stored session: provider=anthropic, model=claude-opus-4-8, agentRuntime.id=claude-cli

Expected behavior

Execution metadata should be populated from the resolved runtime/provider/model returned by the started subagent run, not hardcoded before runtime resolution. At minimum, an inherited/unknown engine should not be labeled Codex.

Environment

  • OpenClaw 2026.7.1
  • Assigned agent configured with primary anthropic/claude-opus-4-8 and agentRuntime.id=claude-cli

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.no-staleExclude from stale automation

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions