Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 81619c6e2a
ℹ️ 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".
| if (existsSync(envLocalPath)) { | ||
| config({ path: envLocalPath }) | ||
| } else if (existsSync(envPath)) { | ||
| config({ path: envPath }) |
There was a problem hiding this comment.
The new dotenv loading logic only reads .env when .env.local does not exist, so Drizzle commands now fail if a repo has a partial .env.local and keeps POSTGRES_URL in .env (a common local setup). In that case POSTGRES_URL remains unset and the hard error is thrown even though a valid fallback file exists. Load both files in precedence order (.env.local first, then .env for missing keys) to preserve the documented fallback behavior.
Useful? React with 👍 / 👎.
| "idx": 28, | ||
| "version": "7", | ||
| "when": 1776910000000, | ||
| "tag": "0028_solid_lockjaw", | ||
| "breakpoints": true |
There was a problem hiding this comment.
This commit registers migration 0028_solid_lockjaw in _journal.json, but there is no corresponding lib/db/migrations/meta/0028_snapshot.json (snapshots currently stop at 0027_snapshot.json). Without that snapshot, future drizzle-kit generate runs diff against stale metadata and can repeatedly re-generate the same default-change migration, causing migration drift and noisy duplicate SQL.
Useful? React with 👍 / 👎.
1 participant
What changed
This change converges the app around a Sealos-specific Codex execution flow instead of the older multi-agent, multi-entry UX.
It removes legacy home page and multi-repository UI paths, simplifies repository and task surfaces, updates the database schema and migration set for the new flow, and rewrites the project documentation to match the current product direction.
Why it changed
The repository had drifted between an older generic coding-agent template and the newer Sealos-focused product direction.
This PR makes the product surface, schema, and documentation line up with the current execution model: a fixed
codex+gpt-5.4path running through Devbox and the Codex Gateway.Developer impact
reference/.Validation
pnpm formatpnpm type-checkpnpm lint(warnings only, no errors)