Agent provider config is inconsistent across install, CLI, and config

[ClintonSarkar]

Summary

The coding agent's provider configuration is described three different ways across the installers, the management CLIs, and the config template. The provider name, the connection URL, and the credential all disagree, so at most one path can actually connect the agent to the proxy — and it is unlikely the Linux command-line path has been verified end to end.

Motivation

When a user runs the tool, the agent needs to know where to send requests. Today:

• The installers register a provider under one name; the CLIs export settings under a different name; the config file names a third.
• The installers point the agent at one connection path; the CLIs point it at a slightly different path.
• One platform's CLI sends one placeholder credential; the other platform's CLI sends a different one.

These inconsistencies mean the "start" command and the "install" step may configure the agent differently, and a user could end up with a setup that silently fails to route through the subscription proxy. The naming and URL should be unified to a single source of truth so that install and start always agree.

Acceptance

• The provider name is identical across the installers, both CLIs, and the config template.
• The connection URL the agent uses is identical across install and start.
• The credential value is consistent across platforms.
• A fresh install followed by "start" connects the agent through the proxy on both Linux and Windows.

---

🤖 Generated with Claude Code

[ClintonSarkar]

Resolved across the three installer-hardening PRs that just merged:

• Linux side (CLI + install.sh): Harden Linux installer: stop bin-dir wipe, fix unparseable script, ARM, portability #11
• Windows side (CLI + install.ps1): Harden Windows installer: stop config wipe, ARM64, reliable stop, honest status #12
• Config template + docs: Remove dead release workflow; make config + architecture docs honest #13

The coding-agent provider is now defined in one place (opencode.json, id ccproxy-claude) with a correct address and API key on both platforms; the CLIs no longer export a divergent provider definition, and the config template no longer advertises a conflicting provider name.

---

🤖 Generated with Claude Code