Proposal: explore interoperability conventions for AI coding
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Hi Codex team,
I recently created opinionated-ts/ai-spec, an early community-driven effort to explore an open specification for interoperability between AI coding assistants and development environments.
The repository was created only recently, and this project is intentionally at a very early stage. The specification is not yet stable or finalized. The goal is to involve the ecosystems and communities that are already solving these problems before conventions become independently established and difficult to reconcile later.
The project is focused on exploring common conventions around areas such as:
- Agents
- Hooks
- Plugins
- Instructions and configuration
- Discovery and precedence
- Lifecycle behavior
- Project-level AI configuration
- Other conventions that may benefit from interoperability
The goal is not to replace Codex, abstract its implementation, or require Codex to adopt a particular architecture.
Instead, ai-spec is intended to provide a neutral, community-driven place where existing approaches can be compared, discussed, and potentially standardized where interoperability provides real value.
The repository currently contains the initial project structure, contribution guidelines, and discussion process. Contributors are encouraged to examine existing implementations and prior art before proposing conventions.
I would particularly appreciate feedback from the Codex team on:
- Which existing Codex conventions should be considered important prior art.
- Which areas you believe would benefit from interoperability.
- Which behaviors should remain implementation-specific.
- Whether there are existing efforts or constraints that should be considered before defining common conventions.
- Whether the Codex team or community would be interested in participating while the specification is still being shaped.
Repository and discussion
Repository: https://github.com/opinionated-ts/ai-spec
Contributing: https://github.com/opinionated-ts/ai-spec/blob/main/CONTRIBUTING.md
Discussions: https://github.com/opinionated-ts/ai-spec/discussions
This is intentionally an early-stage initiative rather than a request for immediate adoption.
The goal is to start the conversation early, collect real-world prior art, and give the different ecosystems and their communities an opportunity to influence the direction of the specification before it becomes mature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked opinionated-ts/ai-spec repository, its CONTRIBUTING.md, and its discussions, then compare the conventions it proposes with Codex's existing behavior. This issue is done when the relevant Codex prior art, interoperability opportunities, and implementation-specific constraints have been documented or discussed with the project team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai-infra-agents, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100