Codex

OpenAI Codex is an artificial intelligence model developed by OpenAI. It parses natural language and generates code in response. It is used to power GitHub Copilot, a programming autocompletion tool. Codex is a descendant of OpenAI's GPT-3 model, fine-tuned for use in programming applications. OpenAI has released an API for Codex in closed beta. Based on GPT-3, a neural network trained on text, Codex has additionally been trained on 159 gigabytes of Python code from 54 million GitHub repositories. You can find more information here https://openai.com/blog/openai-codex/

General
Relese dateAugust 31, 2021
AuthorOpenAI
Repository-
TypeAutoregressive, Transformer, Language model

Start building with Codex

We have collected the best Codex libraries and resources to help you get started to build with Codex today. To see what others are building with Codex, check out the community built Codex Use Cases and Applications.


Boilerplates

Kickstart your development with a Codex based boilerplate. Boilerplates is a great way to headstart when building your next project with Codex.

  • Codex Boilerplate Create a function just by typing what it should do, with help of OpenAI Codex.

Libraries

A curated list of libraries and technologies to help you build great projects with Codex.


Codex top builders

Explore the top contributors showcasing the highest number of Codex app submissions within our community.

OpenAI Codex AI technology Hackathon projects

Discover innovative solutions crafted with Codex, developed by our community members during our engaging hackathons.

SourceCourt Exact Lite

SourceCourt Exact Lite

SourceCourt Exact Lite is a bounded, evidence-first research assistant built for AMD AI League Match 4. It answers source-grounded questions while refusing to invent certainty when the available evidence does not support an exact answer. The system retrieves and parses bounded HTTP/HTTPS sources, interprets a user’s question, identifies relevant evidence, ranks candidate passages and links, and extracts an exact answer only when the evidence is sufficient. When the answer is ambiguous, unsupported, or unverifiable, SourceCourt refuses rather than fabricating a result. The project was hardened against unsafe retrieval behavior. Its transport layer rejects private and loopback network targets, protects against SSRF and DNS rebinding, preserves TLS hostname verification, limits redirects, constrains response size and timing, and avoids unsafe proxy behavior. It also includes bounded resource use, deterministic error handling, citation checks, and explicit ambiguity/refusal behavior. SourceCourt Exact Lite is packaged as a real command-line product. It can be installed as a Python package, run locally, or executed from a container image. The public release includes reproducible setup instructions, a deterministic demo, and a security-focused test suite. The release is provider-neutral at the model-adapter boundary, keeping retrieval, ranking, evidence extraction, citation, refusal, and safety logic independent from any single model provider while allowing the official Match 4 runtime or grader to supply the required model configuration. Container: `ghcr.io/null007void/sourcecourt-exact-lite:1.1.2` Digest: `sha256:39cd2d31e6fb95219da190d12a5620868e68293ac6ad88f8659142b744e4feec` SourceCourt Exact Lite returns the exact answer when the source supports it, shows the supporting evidence, and refuses when the result cannot be verified.

GOA: Shop from a Sentence

GOA: Shop from a Sentence

Shopping starts with a need, not always a product name. Alice is graduating in Cape Town. She wants a green, elegant, reusable outfit for a warm December day, but conventional keyword searches leave her bouncing between shops. Independent designers remain hard to discover, while merchants cannot see what customers tried to find. GOA: Shop from a Sentence is a working creative-commerce prototype built by Busi Ndlovu and Kholofelo Robyn Rababalela for the AMD Developer Hackathon Act III, Track 3: Reinvent Commerce. A shopper describes an outfit in natural language or supplies reference photos. Gemma-4-31B-IT through AMD Token Factory interprets the brief into garment, footwear and accessory needs. Semantic catalogue matching proposes items; deterministic Python rules verify size availability, stock, arrival before the event and budget including delivery. Shoppers can swap pieces, ask why they fit, save a look and explicitly send demo quote enquiries. Unmet needs are shown honestly as "not on offer yet" and recorded in a maker demand-gap view. We evaluated GOA using 20 frozen briefs, 20 live Gemma calls and the same synthetic catalogue for a keyword-search baseline. GOA produced 55% fully valid looks versus 30%, 100% first-shown item grounding versus 82%, and 80% sendable enquiries versus 35%. Median steps were 3 versus 8, and GOA captured 12 unmet parts versus none for the baseline. Keyword search filled more individual parts (93% versus GOA's 83%), so our claim focuses on verified outcomes, not superficial coverage. The prototype runs on Vercel. Merchants, product inventory and quote inbox are fictional demo data; no purchases, actual merchant fulfilment or sales uplift are claimed. GOA demonstrates a more accountable bridge between human imagination and available supply.

OpenLoop

OpenLoop

Industrial shift logs record what operators wrote, not what remains unfinished. Technicians leave free-text notes covering machine status, maintenance work, delayed reports, and corrections. When a note logs a pending safety test and a later note says the pump is operating normally, or a backdated entry arrives after a task was reopened, incoming supervisors must manually reconcile what is still open before the next operating window. OpenLoop is an evidence-based semantic reconciliation layer for industrial shift handovers. Instead of asking an LLM to summarize notes or maintain state in prompt memory, OpenLoop separates semantic extraction from state resolution: 1. Semantic Extraction (Gemma-4-31B-IT): Reads each unstructured shift note against the equipment and task registry and emits strict JSON containing typed assertions (pending, completed, status, retract), a mandatory verbatim substring quote, and a resolved occurrence timestamp via an OpenAI- compatible HTTPS adapter. Ambiguous equipment references are routed to supervisor review rather than guessed. 2. Deterministic Python Evidence Ledger: Verifies that every quote appears literally in the source note, isolates equipment operating status on a separate rail from task obligations, filters available knowledge by recording time (recorded_at), and resolves task state from the latest active assertion by occurrence time (occurred_at). Explicit corrections withdraw prior claims by ID without deleting historical records. Across two runs of a four-way benchmark on four synthetic held-out sequences (12 checkpoints per run), OpenLoop produced correct documented task states at 19 of 24 planned checkpoints (12/12 in Run 1; 7/12 in Run 2 with 5 client 45s timeouts) and zero false closures among its 19 valid checkpoints, while the full-history LLM baseline produced false closures at the same two checkpoints in both runs.