[codex] overhaul Mogplex docs structure#38
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Mogplex PR Review
Status: Attention needed
This is a large, well-structured docs overhaul that reorganizes Mogplex's information architecture around jobs-to-be-done rather than CLI-vs-web surface split. The content is internally consistent and cross-linked. There are no security issues or broken code. I found a handful of real issues worth addressing before merge: one truncated/incomplete page in the diff, one undocumented environment variable introduced without explanation, and several stale or incorrect cross-references within the content.
2 findings were added inline.
Warnings
review-and-triage.mdxlinks to/web/guides/github-mention-routingbut the PR routes that under/web/guides/(content/docs/capabilities/review-and-triage.mdx)
Line 17 of the new file links to/web/guides/github-mention-routing, which is referenced in many new files. That path is not a new file in this PR — it is an existing page undercontent/docs/web/guides/. This is fine, but theintegrations/index.mdxand several other new pages also reference/integrations/slack,/integrations/vercel, and/integrations/github— all of which ARE new files in this PR. If any of these were missed during the rename/move, links would 404. The PR description confirms a Playwright smoke test over 9 docs routes passed, but it is not clear whether all the new cross-link targets were included in that smoke set. Consider extending the smoke test to cover the new/integrations/*,/platform/*,/capabilities/*,/configure-and-extend/*,/guides/*, and/reference/*routes.
Suggestions
- web/meta.json adds
modelspage butcontent/docs/web/models.mdxis truncated in the diff (content/docs/web/models.mdx)
The diff for this file ends atThe default m(patch line 134 of 134 changes), mid-sentence. Likeconnections-and-mcp.mdx, the full file from the head branch is complete. This is a GitHub patch-viewer truncation artifact, not a real content issue — but sincemodelsis now linked in the sidebar viaweb/meta.json, it is worth confirming the full page renders in the build. $AGENTS_HOMEenvironment variable referenced in custom-slash-commands.mdx without definition (content/docs/configure-and-extend/custom-slash-commands.mdx)
The 'Where commands live' section lists$AGENTS_HOME/commands/**/*.mdas a user-scope command path, but$AGENTS_HOMEis not defined or mentioned anywhere else in the docs — includingconfiguration-and-flags.mdx, which documents the full environment variable table. Either$AGENTS_HOMEshould be added to the env-var table inconfiguration-and-flags.mdxwith a note that it defaults to$MOGPLEX_HOME, or the reference here should be changed to$MOGPLEX_HOMEif they are the same variable.- Hardcoded date in API Quickstart example response (
2026-05-17) (content/docs/web/api/quickstart.mdx)
The representativebranch.workingvalue in the run-start response example readsmogplex/run/2026-05-17/inspect-tests. Hardcoded dates in docs examples age poorly and can confuse readers who see a date in the future (today) or in the past (later). Use a placeholder like<date>orYYYY-MM-DDinstead:mogplex/run/YYYY-MM-DD/inspect-tests.
| <Card title="Connection Scope and Overrides" href="/web/guides/connection-scope-and-overrides" /> | ||
| <Card title="MCP Servers API" href="/web/api/mcp-servers" /> | ||
| <Card title="Security and Data Handling" href="/reference/security-and-data-handling" /> | ||
| </Cards> |
There was a problem hiding this comment.
Warning: configure-and-extend/connections-and-mcp.mdx diff is truncated mid-sentence
The diff for this file ends mid-sentence: On startup, the CLI can use the remot (patch line ~140 of 140 changes). The full file fetched from the head branch is complete, so the truncation is only in GitHub's patch display — the actual committed file is fine. However it's worth verifying the build renders the complete file, because any line-count mismatch in the patch viewer can hide a real edit that got dropped.
| @@ -9,6 +9,7 @@ const withMDX = createMDX(); | |||
| /** @type {import('next').NextConfig} */ | |||
| const config = { | |||
| reactStrictMode: true, | |||
There was a problem hiding this comment.
Warning: allowedDevOrigins added to next.config.mjs without explanation
The change adds allowedDevOrigins: ['127.0.0.1'] to Next.js config. This is not mentioned in the PR description, and it's not obviously related to the docs IA overhaul. In Next.js 15, allowedDevOrigins controls which origins can access the dev server without triggering a CORS warning/block, which means it slightly widens development connectivity. This is low-risk in dev, but the value '127.0.0.1' already resolves to localhost — it's unclear whether this was added to fix a specific dev-environment problem or was left in by accident. A comment explaining the reason would prevent future confusion, and it should not appear in production builds.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee5f746657
ℹ️ 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".
| The first useful question is simpler: | ||
| <Callout title="Documentation index"> | ||
| Fetch the complete docs index at [`/llms.txt`](/llms.txt). Use | ||
| [`/llms-full.txt`](/llms-full.txt) when you need the full text of every docs |
There was a problem hiding this comment.
Point docs index to an existing full-text endpoint
The new callout instructs readers to use /llms-full.txt, but this repository does not define that route (only /llms.txt and /llms.mdx/... are implemented under src/app). Following this guidance currently returns 404, so agents/users trying to consume the “full text of every docs page” from the homepage will fail unless this link is changed to a real endpoint or the route is added.
Useful? React with 👍 / 👎.
Summary
Validation
Need help on this PR? Tag
@codesmithwith what you need.