OPENJELLYFISH ACADEMY · 03
Connect Codex and Cursor subscriptions
The host owner signs in and grants model access; admins then choose their engine.
Steps and explanations
01The host owner starts the connection
The host owner manages subscription connections. Open the host console and authenticate with its host key. An ordinary admin receives a grant instead.
Try it · Open /superadmin and locate 超管 key and 进入超管控制台.
02Create a recognizable connection
Choose Codex or Cursor under engine connections, give it a recognizable name, and create it. Creating a connection does not sign the account in.
Try it · Select 连接引擎, enter Teaching Codex in 连接名称, then select 创建连接.
03Complete sign-in on the official page
Codex offers device-code or local-browser sign-in; Cursor uses browser sign-in. Complete authorization on the official page, then wait for Connected status.
Try it · Illustrate 设备码登录(服务器) → 登录 Codex → 打开官方登录页面 without a real code.
04Grant access by admin and model
Under trusted-admin sharing, choose an admin and the models they may use, then save the grant. They share account limits while keeping separate admin chats and files.
Try it · Choose 选择可信 admin and 授权模型, then select 保存授权.
05The admin chooses a default engine
Back in Models & connections, the admin finds the team connection. Choose and save a default engine, connection, and model; existing conversations keep their connection.
Try it · Open 新聊天默认引擎, choose a connection and model, then select 保存默认引擎.
06Handle unavailable connections correctly
If reauthorization or process recovery is required, ask the host owner to resolve it. An account change can invalidate grants; changing your prompt will not fix that.
Try it · Show 账号已变更,需重新授权 and locate 编辑 / 重新授权 in the host console.
07Verify the connection in a new chat
Create a chat and select an authorized Codex or Cursor model. This uses the subscription connection; it does not enable the client’s native Plan mode.
Try it · Select New chat, choose a model under the team connection, and illustrate a simple question.
What you will learn
Separate host sign-in, admin grants, and the default engine for new chats.
Before you start
- The host has enabled and installed the CLI engine, and its owner has a usable subscription account.
- Admins need a host grant. No real keys, device codes, or accounts appear here.