feat(cli): port supabase start command to native TypeScript by Coly010 · Pull Request #5847 · supabase/cli

Coly010 · 2026-07-09T15:48:08Z

What changed

Ports supabase start from a Go-binary proxy to native TypeScript in the legacy CLI shell (CLI-1323), continuing the local-dev-stack shell migration alongside the already-ported stop/status/db push/db reset/db start.

Talks directly to Docker/Podman via subprocess, mirroring Go's sequential per-container DockerStart — no Docker Compose, and no @supabase/stack/effect orchestration (that runtime targets a deliberately different local-dev product and would silently manage the wrong set of containers). Brings up all 14 containers in Go's real start order, with per-service config-boolean + --exclude gating, Go-byte-exact env/image resolution, a bulk health-check phase (Docker healthcheck for most services, an HTTP-HEAD-through-Kong bypass for PostgREST/Edge Runtime), and full rollback on any bring-up failure.

Also natively implements the fresh-volume DB schema/migration/seed pipeline, Edge Runtime container bring-up, and fresh-volume storage bucket seeding — previously tracked as out-of-scope follow-ups for this port, now closed. Only the linked-project version-check suggestion (a best-effort "update available" hint with zero Management API dependency otherwise) remains out of scope by design.

Why

Continues the legacy-shell migration from Go-binary-proxy commands to native TypeScript, closing CLI-1323.

Reviewer-relevant context

legacyParseGoDuration (the config.toml duration-string parser feeding Go-parity env vars like GOTRUE_SESSIONS_TIMEBOX) silently accepted a malformed duration with no digits (a bare unit like "s", or a lone "." with no digits on either side) and returned 0 instead of erroring like Go's real time.ParseDuration — both cases now throw Go's exact time: invalid duration "..." message.
start.services.ts's descriptive enabledGate metadata for Mailpit referenced the deprecated inbucket config section instead of its local_smtp rename. Fixed, and added a mechanical cross-check test that evaluates every service's enabledGate string against start.gates.ts's real computed gate across a battery of synthetic configs, so a future drift between the two fails loudly instead of silently.
Confirmed and closed the PostgREST health-check's TLS/CA trust gap for [api.tls] enabled = true local stacks (self-signed Kong cert) — the local-Kong-CA-trust mechanism already used by seed buckets/storage/db reset is now wired into start's health-check HTTP client too.

Note

This branch is currently 9 commits behind develop (unrelated deps/docker bump commits) — opening as draft to get CI/review visibility; happy to rebase before this comes out of draft.

Ports `supabase start` from a Go-binary proxy to native TypeScript in the legacy CLI shell (CLI-1323), continuing the local-dev-stack shell migration alongside the already-ported `stop`/`status`/`db push`/`db reset`/`db start`. ## What changed Talks directly to Docker/Podman via subprocess, mirroring Go's sequential per-container `DockerStart` — no Docker Compose, and no `@supabase/stack/effect` orchestration (that runtime targets a deliberately different local-dev product and would silently manage the wrong set of containers). Brings up all 14 containers in Go's real start order, with per-service config-boolean + `--exclude` gating, Go-byte-exact env/image resolution, a bulk health-check phase (Docker healthcheck for most services, an HTTP-HEAD-through-Kong bypass for PostgREST/Edge Runtime), and full rollback on any bring-up failure. Also natively implements the fresh-volume DB schema/migration/seed pipeline, Edge Runtime container bring-up, and fresh-volume storage bucket seeding — previously tracked as out-of-scope follow-ups for this port, now closed. Only the linked-project version-check suggestion (a best-effort "update available" hint with zero Management API dependency otherwise) remains out of scope by design. ## Notable review-driven fixes - `legacyParseGoDuration` (the `config.toml` duration-string parser feeding Go-parity env vars like `GOTRUE_SESSIONS_TIMEBOX`) silently accepted a malformed duration with no digits (a bare unit like `"s"`, or a lone `"."` with no digits on either side) and returned `0` instead of erroring like Go's real `time.ParseDuration` — both cases now throw Go's exact `time: invalid duration "..."` message. - `start.services.ts`'s descriptive `enabledGate` metadata for Mailpit referenced the deprecated `inbucket` config section instead of its `local_smtp` rename. Fixed, and added a mechanical cross-check test that evaluates every service's `enabledGate` string against `start.gates.ts`'s real computed gate across a battery of synthetic configs, so a future drift between the two fails loudly instead of silently. - Confirmed and closed the PostgREST health-check's TLS/CA trust gap for `[api.tls] enabled = true` local stacks (self-signed Kong cert) — the local-Kong-CA-trust mechanism already used by `seed buckets`/`storage`/ `db reset` is now wired into `start`'s health-check HTTP client too. Closes CLI-1323

github-actions · 2026-07-09T15:48:23Z

👋 Thanks for the contribution! This pull request isn't linked to a tracked issue, so it's being closed automatically.

Please open an issue first, wait for a maintainer to add the open-for-contribution label, then open a pull request that links the issue with a closing keyword (e.g. Closes #123).
See CONTRIBUTING.md for the full workflow. Once a maintainer adds the open-for-contribution label to a linked open issue, reopen or open a new pull request and it will be accepted.

…3-port-supabase-start

github-actions · 2026-07-09T16:27:03Z

👋 Thanks for the contribution! This pull request isn't linked to a tracked issue, so it's being closed automatically.

Please open an issue first, wait for a maintainer to add the open-for-contribution label, then open a pull request that links the issue with a closing keyword (e.g. Closes #123).
See CONTRIBUTING.md for the full workflow. Once a maintainer adds the open-for-contribution label to a linked open issue, reopen or open a new pull request and it will be accepted.

github-actions · 2026-07-09T16:30:41Z

👋 Thanks for the contribution! This pull request isn't linked to a tracked issue, so it's being closed automatically.

Please open an issue first, wait for a maintainer to add the open-for-contribution label, then open a pull request that links the issue with a closing keyword (e.g. Closes #123).
See CONTRIBUTING.md for the full workflow. Once a maintainer adds the open-for-contribution label to a linked open issue, reopen or open a new pull request and it will be accepted.

github-actions · 2026-07-09T17:05:51Z

👋 Thanks for the contribution! This pull request isn't linked to a tracked issue, so it's being closed automatically.

Please open an issue first, wait for a maintainer to add the open-for-contribution label, then open a pull request that links the issue with a closing keyword (e.g. Closes #123).
See CONTRIBUTING.md for the full workflow. Once a maintainer adds the open-for-contribution label to a linked open issue, reopen or open a new pull request and it will be accepted.

) The contribution gate identified internal maintainers solely from the PR's `author_association`, which GitHub only reports as `MEMBER` when a user's organization membership is public. A private org member (e.g. a `supabase/cli` team member who keeps membership private) is reported as `CONTRIBUTOR`/`NONE`, so the gate wrongly closed their PRs as "no-linked-issue" (see supabase#5847). Resolve maintainer status from the author's effective repository permission (`admin`/`write`), which reflects team/org-granted access that `author_association` does not surface, falling back to it only when the cheap signals (bot, public internal association) are inconclusive. The permission endpoint needs just `Metadata: read`, already covered by the workflow's `contents: read`. Claude-Session: https://claude.ai/code/session_01D41gYiFBSU7adE4ppnUUKg --------- Co-authored-by: Claude <noreply@anthropic.com>

Coly010 · 2026-07-10T08:56:06Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 623dd8b18e

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Coly010 · 2026-07-10T09:14:59Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 623dd8b18e

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

supabase start's TS port had five spots where Go's real behaviour was silently dropped: - supabase/.temp/storage-migration (the linked project's Storage migration pin) was never read, so DB_MIGRATIONS_FREEZE_AT was always empty on a fresh DB setup and the Storage container itself. - supabase/.temp/{gotrue,rest,storage,realtime,studio,pgmeta,logflare, pooler}-version pins were never applied to the images start pulls/creates, unlike Go's Config.Load rewrite. Hoisted the existing services command's reader into shared/legacy-service-version-overrides.ts and reused services.shared.ts's tag-rewrite helpers instead of a third copy. - --network-id was read by several other native ports but never by start itself, so the override never reached any container or the Docker network start creates. - SUPABASE_API_PORT's env override was computed for status URLs but never exposed for Kong/Edge Runtime's own container specs, so they kept publishing/binding the un-overridden config.api.port. - Studio's function bind mounts were hardcoded to [], unlike Go's unconditional (Edge-Runtime-independent) PopulatePerFunctionConfigs call — extracted the existing per-function bind computation in shared/functions/serve.ts into a reusable resolveFunctionBindMounts so both callers share one calculation.

Coly010 · 2026-07-10T10:14:12Z

@codex review

chatgpt-codex-connector · 2026-07-10T10:14:22Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

…l in start Three more Go-parity gaps in supabase start found by review: - db.root_key (including encrypted: values) was never resolved or passed to the Postgres container, so every project booted with the hard-coded default pgsodium key instead of a customized one, breaking decryption of existing encrypted data. Resolved in legacyResolveLocalConfigValues off the raw config document (unmodeled in @supabase/config's schema), reusing the existing decrypt helpers. - DockerStart's Linux-only host.docker.internal:host-gateway mapping was already correctly ported for the one-shot migrate jobs and Edge Runtime bring-up, but never made it into the common legacyStartContainer path the other 13 services go through. - auth.external_url (also unmodeled in the schema, with its own Go regression test) was never read, so GoTrue's API_EXTERNAL_URL/JWT issuer default/mailer verify URL/OAuth redirect fallbacks always derived from apiUrl even when a project intentionally exposed auth at a different host.

Coly010 · 2026-07-10T10:39:35Z

@codex review

chatgpt-codex-connector · 2026-07-10T10:39:45Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

…es tag ordering Three more Go-parity gaps found by review: - [auth.email.smtp] present without an explicit enabled key should default to enabled (Go sets this at load time), but the schema always decodes enabled: false when the key is absent, so GoTrue silently fell back to Mailpit. Reuses the existing correct resolution already implemented for config validation, exposed as legacyResolveAuthEmailSmtp. - auth.external providers outside the schema's fixed ~19-provider set (e.g. a custom [auth.external.my_oidc] block) never reached GoTrue's env, even though Go's Auth.External is a genuine map iterated unconditionally and this port's own config validation already accepts arbitrary provider names. Reuses the same raw-document iteration validateAuthExternalProviders already established. - A registry override with a port (SUPABASE_INTERNAL_IMAGE_REGISTRY= localhost:5000) broke the Postgres version-tag comparison, since Go compares the pre-registry-rewrite image while this port was comparing the already-rewritten one. Threaded the original image through as a separate configImage field used only for that comparison.

Coly010 · 2026-07-10T11:07:34Z

@codex review

chatgpt-codex-connector · 2026-07-10T11:07:44Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-11T17:28:47Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e5cd58c9a

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-11T17:55:38Z

+      Effect.ensuring(
+        Effect.suspend(() =>
+          legacyCleanupStartSecrets(cliConfig.workdir, containerNamesBeforeTeardown),
        ),


Avoid deleting secrets before teardown succeeds

When legacyDockerRemoveAll fails after the initial listing, this ensuring still deletes staged secret directories for every listed container. In scenarios such as docker stop failing for one container or container prune failing after stops, some containers can remain live or at least restartable with bind mounts pointing at these files, so a failed supabase stop can break the remaining stack by removing its TLS/JWT/pgsodium/pooler secrets. Limit this cleanup to containers confirmed removed, or run it only after teardown has succeeded.

Useful? React with 👍 / 👎.

Coly010 · 2026-07-11T18:25:54Z

@codex review

chatgpt-codex-connector · 2026-07-11T18:26:01Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-11T19:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-11T19:25:58Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-11T20:26:04Z

@codex review

chatgpt-codex-connector · 2026-07-11T20:26:12Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-11T21:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-11T21:26:01Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-11T22:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-11T22:26:01Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-11T23:25:51Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e5cd58c9a

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-12T00:02:14Z

+export const legacyStartEdgeRuntimeContainer = Effect.fn("legacy.start.edgeRuntime")(function* (
+  input: LegacyEdgeRuntimeBringUpInput,
+) {
+  return yield* startEdgeRuntimeContainer({


Preserve Podman fallback for Edge Runtime start

When Docker is absent but Podman is installed, this default Edge Runtime path now delegates to startEdgeRuntimeContainer, whose setup/run/reload flow still calls helpers that hard-code runChildProcess("docker", ...) instead of the spawnContainerCli Docker/Podman fallback used by the rest of native start. Because edge_runtime.enabled defaults to true, supabase start can get through the earlier image/container steps via Podman and then fail as soon as it reaches Edge Runtime; thread the same container-CLI fallback through this path too.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-12T00:02:14Z

+  return legacyInspectDockerContextHost(spawner).pipe(
+    Effect.orElseSucceed(() => legacyPlatformDefaultDockerHost(platform)),


Resolve Vector's socket from the active container CLI

On a Podman-only host with analytics enabled (the default) and no DOCKER_HOST, the rest of native start can use the Podman fallback, but this resolver still probes only docker context inspect and then falls back to Docker's default /var/run/docker.sock. Vector then gets a bind mount for a Docker socket that does not exist instead of the Podman socket, so supabase start can fail at the Vector container (or start it without log access); derive this host from the same selected container runtime or add a Podman-aware socket fallback.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-12T00:02:14Z

+        const binds = await Promise.all(
+          secretFiles.map(async (secretFile, index) => {
+            const hostPath = join(dir, `secret-${index}`);
+            await writeFile(hostPath, secretFile.content, { mode: 0o600 });


Keep staged secrets readable by container users

When these files are bind-mounted into Postgres/Kong/Supavisor on Linux, Docker preserves the host file mode and numeric owner; with 0600 owned by the invoking host user, non-root service users inside the images cannot read the mounted pgsodium key/Kong config/pooler script. The Go path wrote the same contents inside the container via the entrypoint heredoc, so they were readable there; keep the parent directory private but make the staged files container-readable, or copy/chown them before exec.

Useful? React with 👍 / 👎.

Coly010 · 2026-07-12T00:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-12T00:25:59Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-12T01:25:53Z

@codex review

chatgpt-codex-connector · 2026-07-12T01:26:02Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-12T02:25:53Z

@codex review

chatgpt-codex-connector · 2026-07-12T02:26:01Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-12T03:25:55Z

@codex review

chatgpt-codex-connector · 2026-07-12T03:26:02Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-12T04:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-12T04:25:59Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-12T05:25:51Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e5cd58c9a

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-12T05:50:24Z

+  if (hours > 0) return `${sign}${hours}h${minutes}m${secs}s`;
+  if (minutes > 0) return `${sign}${minutes}m${secs}s`;


Preserve fractional seconds when formatting long durations

When a configured Go-style duration is at least one minute or hour and also has a fractional-second remainder, this returns before including the ms/us/ns portion. For example, auth.sms.max_frequency = "1m0.5s" or a session duration like "1h0.5s" is normalized to 1m0s/1h0m0s instead of Go's 1m0.5s/1h0m0.5s, so the GoTrue container receives a shorter timeout/rate-limit than the Go CLI would set.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-12T05:50:24Z

+            message: `failed to parse config: ${cause instanceof Error ? cause.message : String(cause)}`,
+          }),
+      });
+      yield* legacyWaitForHealthyServices(spawner, [postgresContainerId], {


Honor --ignore-health-check for Postgres failures

With --ignore-health-check, this Postgres wait fails inside bringUp, so the surrounding rollback runs and the command exits non-zero before the later ignore-health-check downgrade is reached. Go applies ignoreHealthCheck && start.IsUnhealthyError(err) to the whole run() error, including StartDatabase's Postgres WaitForHealthyService, so a DB health timeout is supposed to be printed as a warning and still reach the normal status output; this regresses users who intentionally use the flag while Postgres is slow or unhealthy.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-12T05:50:24Z

@@ -576,7 +531,7 @@ const resolveAuthArtifacts = Effect.fnUntraced(function* (
  const shouldUseJwtSecretFallback = signingKeysPath.length === 0;

  const keys: unknown[] = [];
-  const issuerUrl = enabledThirdPartyIssuer(auth.third_party);
+  const issuerUrl = resolveThirdPartyIssuerUrl(auth.third_party);


Keep functions serve lenient when auth is disabled

When auth.enabled = false, Go skips Auth.ThirdParty.validate(), calls ResolveJWKS, and functions serve discards that error (jwks, _ := ...), so malformed or multiple third-party providers do not block local serving. This synchronous validating call happens before the remote-JWKS error swallowing, so configs such as disabled auth with an enabled WorkOS provider missing issuer_url or multiple enabled providers abort supabase functions serve instead of continuing with an empty JWKS.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-12T05:50:24Z

+
+type Spawner = ChildProcessSpawner["Service"];
+
+const DOCKER_PULL_RETRY_DELAYS_MS = [500] as const;


Match Go's two pull retries for transient image pulls

Go calls DockerImagePullWithRetry(ctx, image, 2), which gives each registry candidate the initial pull plus two retries after longer backoffs. With a single 500 ms delay here, the port only makes one retry, so fresh starts fail on transient pull errors that would have succeeded on Go's second retry, especially when many service images are uncached.

Useful? React with 👍 / 👎.

Coly010 · 2026-07-12T06:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-12T06:26:06Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Coly010 · 2026-07-12T07:25:51Z

@codex review

chatgpt-codex-connector · 2026-07-12T07:25:59Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

github-actions Bot closed this Jul 9, 2026

Merge remote-tracking branch 'origin/develop' into columferry/cli-132…

623dd8b

…3-port-supabase-start

Coly010 reopened this Jul 9, 2026

github-actions Bot closed this Jul 9, 2026

Coly010 self-assigned this Jul 9, 2026

Coly010 reopened this Jul 9, 2026

github-actions Bot closed this Jul 9, 2026

avallete mentioned this pull request Jul 9, 2026

ci: exempt private org members from the contribution gate #5848

Merged

avallete reopened this Jul 9, 2026

github-actions Bot closed this Jul 9, 2026

avallete reopened this Jul 9, 2026

chatgpt-codex-connector Bot reviewed Jul 10, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed Jul 11, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed Jul 12, 2026

View reviewed changes

		return legacyInspectDockerContextHost(spawner).pipe(
		Effect.orElseSucceed(() => legacyPlatformDefaultDockerHost(platform)),

		if (hours > 0) return `${sign}${hours}h${minutes}m${secs}s`;
		if (minutes > 0) return `${sign}${minutes}m${secs}s`;


		type Spawner = ChildProcessSpawner["Service"];

		const DOCKER_PULL_RETRY_DELAYS_MS = [500] as const;

Uh oh!

Conversation

Coly010 commented Jul 9, 2026

What changed

Why

Reviewer-relevant context

Note

Uh oh!

github-actions Bot commented Jul 9, 2026

Uh oh!

github-actions Bot commented Jul 9, 2026

Uh oh!

github-actions Bot commented Jul 9, 2026

Uh oh!

github-actions Bot commented Jul 9, 2026

Uh oh!

Coly010 commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Coly010 commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Coly010 commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 10, 2026

Uh oh!

Coly010 commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 10, 2026

Uh oh!

Coly010 commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 10, 2026

Uh oh!

Coly010 commented Jul 11, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jul 11, 2026

Choose a reason for hiding this comment

Uh oh!

Coly010 commented Jul 11, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 11, 2026

Uh oh!

Coly010 commented Jul 11, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 11, 2026

Uh oh!

Coly010 commented Jul 11, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 11, 2026

Uh oh!

Coly010 commented Jul 11, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 11, 2026