Sign in with a ChatGPT or Grok plan
Use the models that come with your ChatGPT or Grok plan in Murage, on Fuigo, Codex and other engines that take model connections, without a separate API key.
ChatGPT and Grok are trademarks of their owners. Murage isn't affiliated with OpenAI or xAI.
Sign in
Step 1
Find the plan buttons
Open SettingsModels and find Use a plan you already have. The note reads Sign in and your bots can use the models that come with your ChatGPT or Grok plan. Plan limits apply.
You're done when: you can see Continue with ChatGPT and Continue with Grok.
Step 2
Sign in
Choose Continue with ChatGPT or Continue with Grok. Your browser opens. The screen reads Finish signing in in your browser. This updates on its own. Finish there and come back.
For Grok, if it is taking a while, copy the code from the x.ai page and paste it under Paste the code from x.ai, then press Finish sign-in.
When it lands you see Signed in. The plan's models now show in the model picker.
You're done when: the row reads Signed in, with your email and the plan name.
Step 3
Give a bot a plan model
Open Bot settingsModel, pick Fuigo or Codex as the engine, and choose one of the plan's models from the list.
You're done when: the bot answers on a model from your plan.
Which engines can use a plan
A plan sign-in is a model connection, so every engine that takes model connections can use it: Fuigo, Codex, and the OpenAI-compatible engines such as Qwen, Hermes and Grok Build. Claude Code is the exception. The picker says so: Claude Code runs Claude models. Pick Fuigo or Codex to use your ChatGPT or Grok plan.
How Murage treats the sign-in
- It signs in with your ChatGPT plan the same way the Codex CLI does, and keeps its own copy. Your Codex CLI login and your Grok Build login are left alone.
- The sign-in is sent only to that provider, and Murage keeps it out of replies and logs.
- The Grok button is marked Unofficial. xAI has not published this sign-in for other apps. If xAI turns it off, use an xAI API key instead. OpenAI may also change or limit how plan sign-ins work.
- Sign out on the row ends it.
When the plan hits its limit
A plan has usage limits. When you hit one, the row reads Plan limit reached. Bots using this plan pick up again after 14:30. Nothing was moved to another provider. with the real time. The bots wait.
To have a bot carry on while the plan is paused, give it a backup engine. See Plan limits and backup engines.
No browser on this computer
A server with no display can still sign in. Choose Sign in with a code. Murage shows a page address and Your sign-in code. Open the page on any device with a browser, enter the code, and the screen in Murage updates on its own.
Troubleshooting
You see
OpenAI did not accept this sign-in. Check that the account has a ChatGPT plan, then try again.Do this
The account you signed in with has no ChatGPT plan. Sign in with the account that does.
You see
xAI did not accept this sign-in. A SuperGrok or X Premium plan is needed.Do this
The X account you used has neither plan. Sign in with one that does, or use an xAI API key in SettingsModels.
You see
Your ChatGPT sign-in ended. Sign in again to keep using it.Do this
Providers end a sign-in after a while. Choose Sign in again on the row. The Grok version reads the same.
You see
That code was not accepted. Start the sign-in again.Do this
The code from the x.ai page was mistyped or had expired. Choose Cancel sign-in, then start again.
You see
Sign-in timed out. Try again.Do this
The browser step took too long. Start again and finish it in one go.
You see
This computer has no display for a browser sign-in. Use Sign in with a code instead.Do this
See "No browser on this computer" above.
You see
Another program is using the sign-in port. Close any open Codex CLI sign-in, then try again.Do this
A Codex CLI sign-in is open in a terminal somewhere. Finish or close it, then try again in Murage.
You see
The operating-system credential store is unavailable, so the sign-in cannot be saved.Do this
Murage saves plan sign-ins in your operating system's credential store. On Linux that means an unlocked keyring. See the next row.
You see
Murage can't save this sign-in yet. This computer has no unlocked keyringDo this
On Linux, install and unlock a keyring such as gnome-keyring or KWallet, restart Murage, then sign in again. Without a keyring, Murage has nowhere to keep the sign-in that only you can open, so it does not save it.
You see
Sign-in works in the installed Murage app on this computer.Do this
You are looking at Murage from a phone or another browser. Do the sign-in on the computer running Murage.
You see
This sign-in is turned off in this version of Murage.Do this
That provider's sign-in is not available in your build. Use an API key for that provider instead.