The Codex verification prompt: checking the install

Paste it into a new session after installing with the Codex install prompt. It checks the connection, the two app tools (create_aiakiv_card, run_aiakiv_app_action), the save location (binding main) and the seven skills one by one, and appends the results to the install record.

After installing with the Codex install prompt, open a new session and paste the prompt below. Codex checks the connection, the tools, the save location and the skills one by one, and appends the results to the install record. This prompt passed a real run on 2026-10-13.

  • Run it in a new session. The session you installed from may not see the newly attached tools and skills yet.
  • If you installed under another name, change the prompt too. If you named the MCP server AiAkivCodex, change AiAkiv in the prompt to AiAkivCodex.
  • It leaves your memory and settings alone. This prompt does not save memories, create cards or change account settings. It writes its results only to the record file in the working folder.

The prompt

Codex follows the prompt in English just as well as the Korean original.

Verify, in a new session, the AiAkiv I just installed on this PC.

1. Check that the AiAkiv MCP server is actually connected.
2. Check that the tool list of that connection provides create_aiakiv_card and run_aiakiv_app_action.
3. You must call get_save_target through the AiAkiv connection. Do not check through a different AiAkiv connection instead.
4. Record the account, team, project, binding, save domain/group and read-only status from the response. Show them to me so I can confirm they match the account I signed in with.
5. Check the names of the installed AiAkiv skills and where they are actually loaded from. In particular, check that aiakiv-contents and aiakiv-console are recognized.
6. Find the aiakiv-install-test.md written during installation and append the verification results to it. If you cannot find it, write aiakiv-verification-test.md in the current test folder.

Mark each item as success, failure or could not check, and attach the actual evidence. Do not save memories, create cards, edit Contents or change account settings.
At the end, briefly summarize the overall result and anything an ordinary user had to prepare in addition.

What you should see

Item Expected result
1, 2. Connection and tools The connection is there, and both create_aiakiv_card and run_aiakiv_app_action are in the tool list. Card creation is on every connection, but run_aiakiv_app_action is on this connection attached with the ?apps=all address and not on AiAkiv Memory installed from the plugin directory
3, 4. Save location binding comes back as "main" and the project name carries (Main). This connection follows the Main project in the console. Check that the account and team match the account you signed in with
5. Skills The seven skills (aiakiv-onboarding, aiakiv-save-and-recall, aiakiv-graph-query, aiakiv-links, aiakiv-cards, aiakiv-console, aiakiv-contents) are read from ~/.agents/skills/. If aiakiv-console and aiakiv-contents show up, you can use app features too
6. Record The verification results are appended to the aiakiv-install-test.md written at install time

To pin a project per folder, use a project-pinned API key rather than this connection → Connecting ChatGPT §2.

If the results differ

  • run_aiakiv_app_action is missing. AiAkiv Memory from the plugin directory may still be installed, and the check may have gone through it. Remove the plugin, or install this connection as AiAkivCodex and check again under that name. A connection whose address lacks ?apps=all doesn't have this tool either → The app action tool.
  • The skills are missing. Run codex debug prompt-input "hello" to print the prompt sent to the model and see whether the seven names are in its skill list. If not, paste the Codex install prompt again. It doesn't install items that are already there a second time.
  • The AI says it can't do console work. Console work that changes something only happens for what you turned on in Reference → AI permissions in the console → Asking your AI to do console work.
Full index → Docs View as Markdown