Install Procurement OS in Codex and ChatGPT

Before you start

Unlock the free download with a work email and extract the edition you need. Check your company’s rules before sending spend files, bids, contracts, or supplier information to an AI service. Use synthetic or approved data for your first test.

Codex needs a project folder you can edit. Python 3 is needed for optional bundled helpers. New Custom GPT creation currently requires an eligible Business, Enterprise, or Edu workspace and admin permission. OpenAI has announced plans to retire Custom GPTs, so confirm availability in your workspace before setup.

Privacy and data handling

The supplied skills, GPT drafts, and Python helpers have no Molecule One upload endpoint or telemetry. The download form records your name and work email; newsletter updates require a separate opt-in. Molecule One does not receive the procurement files you use unless you separately send them to us, such as for support.

Codex and ChatGPT still send the prompts and files you provide to OpenAI for processing. OpenAI says Business, Enterprise, and Edu workspace content is not used to train its models by default. Storage, retention, and access depend on your plan and workspace controls. Check your organisation’s policy and OpenAI’s data controls before using confidential data.

Codex may save settings, outputs, and run history under your project’s .procurement-os/ folder. ChatGPT drafts do not create a Molecule One data store or local history file. Optional web search and the spend dashboard’s external chart library can make separate network requests; avoid these features if your process requires network isolation.

Install the Codex skills

1. Open the project where you will perform procurement work. Create .agents/skills/ if it does not exist.
2. Copy all nine folders from m1-procurement-os-codex/skills/ into the project’s .agents/skills/. Keep each folder’s SKILL.md, references, and scripts together.
3. Copy the edition’s AGENTS.md to the project root. Merge its content if the project already has that file.
4. Open a new Codex chat in the project. Check that the skills appear, then ask for one by name, such as $spend-analyzer.

The package includes a portable plugin.json, but it is not published in a plugin directory. Local skill installation is the supported path for this release. Project settings and run history are saved under .procurement-os/ when the selected workflow uses them.

Set up the ChatGPT drafts

1. In an eligible workspace, open Explore GPTs and select Create on the web.
2. Create one GPT per workflow. Name it Molecule One Procurement OS — <workflow title>.
3. Paste the matching instructions/<skill>.txt into Instructions.
4. Upload the matching knowledge/<skill>-reference.txt and any matching helper reference as Knowledge. Enable Data Analysis for file-heavy workflows if permitted.
5. Test with synthetic data in Preview, then save privately or within your authorised workspace.

The ChatGPT drafts do not run the Codex package’s local scripts or write project memory files. Paste a short organisation profile when needed, and save useful run summaries in your own system.

Your first run

Choose a workflow and provide its source material. These examples work as a starting point:

• Spend analysis: “Analyse this 12-month spend CSV. Show category totals, supplier concentration, missing data, and evidence for three savings opportunities.”
• RFP drafting: “Create an RFP from this statement of work, with weighted evaluation criteria and supplier response instructions.”
• Bid evaluation: “Score these supplier responses against the issued criteria. Cite the source evidence and flag missing answers.”
• Contract review: “Review this MSA from the buyer’s side. Show risks, obligations, renewal dates, and proposed edits for legal review.”

Included workflows

Spend Analyzer · Category Strategy Builder · RFP Generator · RFP Response Evaluator · Supplier Scorecard Engine · Negotiation Playbook Generator · Contract Lifecycle Manager · Supplier Management · ESG Sustainability Assessor

Review and troubleshooting

Before sharing a result, check row counts, exclusions, currencies, units, scoring weights, source citations, contract clauses, and calculations. Procurement, legal, finance, and risk owners retain their normal approval roles.

Codex skill does not appear

Confirm the path is <project>/.agents/skills/<skill-name>/SKILL.md, then reopen the project.

GPT creation is unavailable

Check your workspace type and administrator permissions. Personal ChatGPT accounts currently cannot create new GPTs.

The output seems wrong

Ask for the formulas, source rows, assumptions, and missing data; correct the input and rerun.

Platform references: OpenAI skills, plugin packaging, and GPT creation.