feat(app-server): expose CODEX_COMPANION_APP_SERVER_DISABLE_BROKER env var

[tyoon10]

Closes #602.

Summary

CodexAppServerClient.connect() already accepts options.disableBroker, but there is no supported way for an integrator to request direct app-server spawn from the environment. This adds CODEX_COMPANION_APP_SERVER_DISABLE_BROKER. When set to true, 1, or yes, the client skips broker discovery and spawns codex app-server directly, giving the caller strict per-job process lifetime without the malformed-endpoint workaround.

Pseudo-diff:

// app-server.mjs
+export const BROKER_DISABLE_ENV = "CODEX_COMPANION_APP_SERVER_DISABLE_BROKER";
+function resolveDisableBroker(options) {
+  if (options.disableBroker !== undefined) return Boolean(options.disableBroker);
+  const raw = options.env?.[BROKER_DISABLE_ENV] ?? process.env[BROKER_DISABLE_ENV];
+  return ["true", "1", "yes"].includes(String(raw).trim().toLowerCase());
+}

 static async connect(cwd, options = {}) {
-    if (!options.disableBroker) {
+    const disableBroker = resolveDisableBroker(options);
+    if (!disableBroker) {

options.disableBroker remains the explicit override. The existing CODEX_COMPANION_APP_SERVER_ENDPOINT behavior is unchanged. New unit tests in tests/app-server.test.mjs cover true, 1, and an explicit option override.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a42211a662

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Honor the disable flag in runtime status

When this environment variable is enabled while either CODEX_COMPANION_APP_SERVER_ENDPOINT or a saved broker session exists, connect() correctly chooses the direct transport, but getSessionRuntimeStatus() in plugins/codex/scripts/lib/codex.mjs:906-914 still reports a “shared session” because it only checks for an endpoint. Consequently, /codex:status and setup output claim jobs are reusing the broker even though every connection bypasses it; apply the same disable-value resolution when determining the displayed runtime mode.

Useful? React with 👍 / 👎.

[tyoon10]

Applied: getSessionRuntimeStatus() now calls resolveDisableBroker() so /codex:status reports direct mode whenever CODEX_COMPANION_APP_SERVER_DISABLE_BROKER is set, even if a broker endpoint or saved session exists. Added tests/codex.test.mjs covering disable-wins-over-endpoint and the default cases.