Problem

OpenClaw stores OAuth credentials in auth-profiles.json, but pi-coding-agent (ModelRegistry/AuthStorage) expects OAuth credentials in auth.json / env.

This mismatch can cause pi-based model discovery to omit OpenAI Codex built-in models (including gpt-5.3-codex-spark) from the registry/catalog, leading to configured,missing entries and discovery inconsistencies.

Change

• Add a small bridge that copies OpenClaw's openai-codex OAuth profile fields (access/refresh/expires) into <agentDir>/auth.json when present.
• Invoke the bridge before loading the pi ModelRegistry (models list) and before building OpenClaw's model catalog.

Tests

• Unit test verifies ensurePiAuthJsonFromAuthProfiles() writes the expected auth.json entry and is idempotent.

Greptile Overview

Greptile Summary

This PR adds a small bridge (ensurePiAuthJsonFromAuthProfiles) that copies OpenClaw’s stored OAuth credentials for the openai-codex provider from auth-profiles.json into <agentDir>/auth.json, which is the format expected by pi-coding-agent’s AuthStorage/ModelRegistry. The bridge is invoked before pi model discovery runs in both the CLI registry listing path and the model catalog loading path, and a unit test validates that the bridge writes the expected auth.json entry and is idempotent.

Confidence Score: 5/5

• This PR appears safe to merge with minimal risk.
• Changes are scoped to writing a single bridge entry into agentDir/auth.json before pi model discovery, with conservative validation (requires access/refresh/expires) and idempotent behavior covered by a unit test. No concrete functional regressions or security issues were identified in the modified call sites.
• No files require special attention

_{Last reviewed commit: 6f62221}

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}