Work in progress ยท Free beta

Prepare with Codex. Import into Root when ready.

Root for Codex is still being tested. It works with plain Markdown in a local Codex Drafts folder on your computer. These drafts are outside your live Root Workspace. A draft becomes a Root note only after you manually import it from Root Chrome.

Work in progress

Still a work in progress

Root for Codex is a free permanent beta that we are actively testing. The skills, installation steps, and compatibility may change as we learn what is genuinely useful. It is distributed as a small local plugin package and is not a Codex listing yet.

The plugin is provided as-is with no guaranteed compatibility, continued availability, support response, service level, or data recovery. Keep backups of local notes you want to keep. Read the Terms and Privacy before installing.

What it does

Find, answer, and prepare.

Root for Codex gives Codex three focused ways to work with Markdown in a local Codex Drafts folder. It does not read or write your live Root Workspace.

  • Find Codex Drafts: Search, list, count, or browse the local drafts you make available to Codex.
  • Answer from Codex Drafts: Answer, summarize, or create a useful brief with named evidence.
  • Manage Codex Drafts: Create, save, or append drafts. You can also delete selected local items or clear the folder after seeing a complete preview and confirming the action.

Deletion only affects the local folder you choose. Confirmed items move to your computer's Trash or Recycle Bin. The plugin keeps the drafts folder and does not delete copies already imported into Root Workspace.

Codex Drafts are also separate from Chrome's Research Draft. Research Draft is one browser-side writing surface inside the Root Chrome experience. Codex Drafts are ordinary local files prepared with Codex.

Simple workflow

Draft locally. Import when you choose.

  1. 1. Work in Codex: Use Root for Codex to find a draft, answer from your drafts, or prepare something useful.
  2. 2. Keep the Markdown: The draft stays in the local Codex Drafts folder you control.
  3. 3. Import into Root: When you want it in Root Workspace, open Root Chrome, choose Import Codex Drafts, and select the folder.
  4. 4. Import again when needed: New files are added, unchanged files are skipped, and edited files update their matching Root notes. Root does not watch the folder in the background.

Already using a folder named Codex notes? Keep it. The plugin and importer continue to support that legacy folder without moving, renaming, or duplicating your files.

Why no MCP or Root API

Use the files you can see.

A local MCP bridge would add another background process and permission surface. A hosted Root API would require an account and service layer. Neither is necessary for the small set of jobs this beta is meant to do.

Root for Codex is not a connection to Root Workspace. It uses ordinary Markdown, deliberate copy and paste, explicit exports, and manual import in Root Chrome. You can see what moves, where it lives, and when it enters Root. The plugin remains useful without a Root account, Root Connect, Google Drive access, or access to your live Root Workspace.

Plugin installation

Download the public beta

Root for Codex is available as a work-in-progress beta download. Install it in Codex first and keep drafts in your local Codex Drafts folder. Import into Root Chrome is a separate, manual step.

Beta download

Root for Codex beta

Download the local plugin package, unzip it somewhere stable, add it as a Codex plugin marketplace, then install Root for Codex from Codex Plugins.

SHA-256: 075fef9b726e3900e0ae8c52df2767bfc8eec15b557ecdba365bb19d5045640c
How to verify the download

Verify the download

Check the file before installing

A checksum lets you confirm the zip you downloaded is the same file Root published. If the checksum does not match exactly, delete the file and download it again from rootworkspace.com.

  • Mac: Run shasum -a 256 ~/Downloads/root-for-codex-beta.zip and compare the result with the SHA-256 above.
  • Windows: Run Get-FileHash "$env:USERPROFILE\Downloads\root-for-codex-beta.zip" -Algorithm SHA256 in PowerShell.
  • Match required: The full checksum should be 075fef9b726e3900e0ae8c52df2767bfc8eec15b557ecdba365bb19d5045640c.

Install steps

Add the plugin to Codex

  • Unzip: Unzip the download somewhere stable, such as ~/Downloads/root-for-codex-beta.
  • Create folder: For a new setup, create Codex Drafts somewhere stable, such as Documents. Existing Codex notes folders remain supported.
  • Add the marketplace: Run codex plugin marketplace add ~/Downloads/root-for-codex-beta.
  • Install in Codex: Open Codex Plugins, or use /plugins in Codex CLI. Then install Root for Codex from the personal marketplace.
  • Start fresh: Open a new Codex chat, or start a new Codex CLI session, so the installed plugin is available.
  • Try Root: In Codex desktop, type @ and select Manage Codex Drafts. In Codex CLI, use $root-save-note. Then ask it to save this as a local draft for Root.
  • Manual Root import: If you want a draft inside Root Workspace, open Root Chrome, choose Import Codex Drafts, and select the local folder. Import is manual; Root does not watch the folder automatically.

Uninstall

Remove the plugin without deleting notes

Remove Root for Codex from Codex Plugins when you no longer want it available. This does not delete Markdown from your Codex Drafts or supported legacy Codex notes folder, or imported notes from Root Chrome.