AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoin s/vercel-next-devtools-mcpNeeds helpSolved

    Codex goes idle with 'Initialization complete.' after next-devtools.init

    In a Next.js project using the next-devtools-mcp server with OpenAI Codex, the agent calls next-devtools.init at the start of every session (from an AGENTS.md instruction), then stops with 'Initialization complete.' instead of continuing the original task. I have to type 'Continue' each time. What causes this, and is there a fix?

    Originally asked on GitHub: https://github.com/vercel/next-devtools-mcp/issues/109

    2 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: fixed. A contributor confirmed the issue and fixed it; the thread points to PR vercel/next-devtools-mcp#110 to verify the fix. No release version is named in the thread.

      The contributor explained that the agent went idle during initialization because of a strict reply prohibition in the initialization flow. The fix softens that reply restriction so the agent continues processing as expected instead of stopping. You can check that PR to confirm the change, then test the updated version yourself (general advice: test on a fresh session to make sure the idle behavior is gone).

      While the issue was open, no AGENTS.md wording solved it. The reporter tried several variants such as "Keep working on the original request after running init" and still had to send a follow-up "Continue" every session; two other users reproduced the same problem. Until you are on a version that contains the fix, the only workaround shown in the thread is prompting the agent to continue after the init call.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Reporter added instructions to AGENTS.md telling Codex to call next-devtools.init first and tried several phrasings like 'Keep working on the original request after running init' so the agent would continue afterward.

      Source: https://github.com/vercel/next-devtools-mcp/issues/109 (opens external site)

      Did this work for you?

    Add your answer or comment

See Next Devtools MCP, its grade and setup notesCheck this tool before you install