Skip to content

Trace a Codex CLI and IDE Montage mismatch

When Montage works in Codex CLI but not the IDE, investigate the shared configuration and active environment before adding another server.

Integrations

How do I trace a Codex CLI and IDE Montage mismatch?

When Montage works in Codex CLI but not the IDE, investigate the shared configuration and active environment before adding another server. Find the differing execution context rather than multiplying definitions that conceal the problem. Compare what each process actually reads before adding entries. Codex’s shared configuration design is relevant evidence, but it cannot guarantee that a local CLI and a separate IDE environment share files or user state.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
Copyable task-specific request
Help me trace a Codex CLI and IDE Montage mismatch. Inspect the mcp_servers.montage table in the configuration used by the failing interface. Request signals_status from the IDE after supported authorization. No writes.
01 / Integrations

Read the shared table

Inspect the mcp_servers.montage table in the configuration used by the failing interface. Compare its URL with the working interface before changing either entry. The configuration comparison should show which environment each interface reads, without copying private token stores into the mismatch report.

02 / Integrations

Compare process environments

Determine whether CLI and IDE actually use the same user environment and configuration location. Sharing a configuration design does not guarantee identical files on different machines. A shared design is not proof that a remote IDE process and a local terminal resolve the same home directory or user settings.

03 / Integrations

Avoid duplicate registration

Keep a correct registration rather than adding an indistinguishable IDE-specific server. Duplicate definitions make later consent and tool-selection evidence harder to attribute to one remote connection. Use one recognizable registration to make later evidence attributable, rather than treating differently named duplicates as harmless troubleshooting artifacts.

04 / Integrations

Refresh the affected interface

Use the IDE’s normal configuration refresh and inspect its Montage tools. A CLI response cannot establish that the IDE loaded the refreshed entry. The refresh result should say whether tools appeared in the failing IDE, not simply whether the configuration file remained syntactically valid.

05 / Integrations

Verify the failing path

Request signals_status from the IDE after supported authorization. If only CLI execution works, retain the IDE environment discrepancy as unresolved rather than claiming both interfaces are connected. If the IDE still cannot execute, report CLI success as comparative evidence only and keep the original failing surface explicitly unverified.

Keep the boundaries clear.

  • Use one recognizable registration to make later evidence attributable, rather than treating differently named duplicates as harmless troubleshooting artifacts.
  • If the IDE still cannot execute, report CLI success as comparative evidence only and keep the original failing surface explicitly unverified.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage