Can Codex use Cornerstones in CI?
Yes. CI can run client and docs checks with product-level access where needed.
Agent-native market data
Market data for Codex agents
Use Cornerstones commands as the repeatable market-context interface for Codex. The agent can verify access, read docs, and reason about market surfaces without receiving backend credentials.
Question
How should Codex agents fetch market context during autonomous implementation or review?
When this problem happens
- Codex sessions often run in isolated workspaces where copied credentials are risky.
- Autonomous patches need reproducible market-context commands for later audit.
- Provider-specific details in generated code make public release and review harder.
Recommended architecture
Codex should treat Cornerstones as the only public market-data contract and leave private integration knowledge to server-side code.
Implementation steps
- Add Cornerstones discovery commands to the task brief before Codex starts coding.
- Use environment-scoped Cornerstones access only for authenticated smoke checks.
- Have Codex record market-context assumptions in tests, docs, or handoff metadata.
- Reject patches that introduce private provider names into public client or website surfaces.
Example workflow
cornerstones-client guide --topic codex
cornerstones-client auth status
cornerstones-client verifyComparison table
| Option | Best for | Tradeoff |
|---|---|---|
| Cornerstones | Agent-native market context | Requires adopting a product-level access model |
| Raw private integration | Human-operated internal systems | Can expose credentials, adapters, and unstable implementation details to agents |
| Static prompt paste | One-off prototypes | No freshness, usage accounting, entitlement boundary, or repeatable evidence trail |
FAQ
What should the task prompt include?
Include the public docs links, expected plan boundary, and a warning not to expose private adapters.
Does this replace tests?
No. Codex still needs repo tests and build checks after using market context.
Why is plan awareness useful?
It stops Codex from assuming premium data exists for Free or unauthenticated flows.