Skip to content
Connected learning · Codex

Study with Codex. Keep your learning in Wizzist.

Codex carries the conversation in your terminal. Wizzist keeps your plan, the practice you choose to save, your checks and your next step. The planner key works today; the learning server follows one deployment.

Create a planner key in Settings Every host and endpoint
Where this stands available

Status on this page is honest.

Today: Codex works with a personal planner key. Not yet: the learning server over OAuth, which waits on the wizzist-codex client registration and then admits pilot accounts only.

After deployment: After that deployment, an admitted pilot account signs in once with codex mcp login and Codex can read your study context, open material you select, propose a plan and save practice you select.

Who can connect: You need a Wizzist student account. A planner key works for any account that can open Settings. The learning connector admits pilot accounts only for now; until self-service admission lands, connecting through it needs Wizzist to admit your account.

Set it up

Copy the step your Codex needs.

Create a planner key in Wizzist Settings under AI assistants first. Keep it out of chat; put it in an environment variable and let the command read it from there.

Codex

available

Your planner from the Codex CLI, with a personal planner key.

Works today for any Wizzist account: Codex reads today's steps and your plans, and can propose a plan if the key allows writes.

  1. Create a planner key in Wizzist Settings under AI assistants and export it as WIZZIST_PLANNER_KEY. 
  2. codex mcp add wizzist-planner --url https://app.wizzist.com/api/v1/planner/mcp --bearer-token-env-var WIZZIST_PLANNER_KEY
  3. Ask Codex what you should do today; it calls the planner's today tool. A plan it proposes waits for your acceptance in Wizzist.

After deployment: The learning server follows one deployment: the wizzist-codex client registration. After it, an admitted pilot account runs codex mcp add wizzist --url https://app.wizzist.com/api/v1/learning/mcp --oauth-client-id wizzist-codex, then codex mcp login wizzist, and approves the Wizzist sign-in that opens in the browser.

What crosses the connection

What Codex can and cannot do with Wizzist.

Codex can

  • Read today's steps and your plans through the planner key, and propose a plan or record a test date when your key allows writes.
  • Think with its own model. Assistant tool calls spend none of your Wizzist credits.
  • After the learning server authorizes: read your study context, open material you select, propose a plan and save the practice you choose.

Codex cannot

  • Send photos of paper work to Wizzist. Practice photos go through the signed-in Wizzist app.
  • Award mastery or grade. Practice saved from a session is labeled reported practice; checks run in Wizzist.
  • Read your past Codex sessions or import them into Wizzist.
  • Buy anything or top up credits.
What every assistant must honor

Wizzist keeps the record. Codex helps.

  • Help can begin without a plan or a saved Notebook page.
  • A plan the assistant proposes waits for the learner to accept it in Wizzist.
  • Save only the practice the learner selects; never the whole conversation.
  • Reported practice is labeled as reported. It is not independent mastery.
  • Wizzist owns checks, grades and the learning record. Assistants read results; they do not write them.
  • Purchases and credit top-ups are not available through an assistant.
Your account, your choices

You decide what crosses the connection.

Every connection goes through a Wizzist sign-in or a key you create. Personal Notebook pages and class materials stay private unless you select one source for a specific request. You can revoke a planner key or disconnect the assistant, correct saved practice, or request an export or clearing of your data in Wizzist. Disconnecting stops future access; it does not erase practice already saved.

How connected data is handled Connected assistant support The guide as Markdown