[Brooooooklyn]

Problem

void secret sync <file> used its own dotenv parser. It uploaded values like sk_live_x # note or "abc" # note exactly as written, with no error. It also could not read export KEY=... lines or multi-line quoted values such as PEM keys.

file line                         before                    after
STRIPE_KEY=sk_live_x # live key   "sk_live_x # live key"    "sk_live_x"
TOKEN="abc" # note                "\"abc\" # note"          "abc"
export API_KEY=abc                error: bad name           "abc"
PEM="-----BEGIN...\nAAAA\n..."    error: bad line 'AAAA'    full PEM
CERT="a\nb"                       "a\\nb" (literal)         "a<newline>b"
PASSWORD=p$BASE                   "p$BASE"                  "p$BASE" (unchanged)

What changed

• parseDotenvFile in packages/void/src/cli/secret.ts now uses Node's util.parseEnv, the same dotenv rules .env loading uses.
• It does not use the shared parseDotenv helper, because that expands $VAR. A $ in a secret must stay as written.
• A leading UTF-8 byte order mark (saved by some Windows editors) is dropped before parsing, as the old parser did. parseEnv would keep it in the first name.
• The secret-name check and its error message are the same as before.

Tests

packages/void/test/unit/secret-sync.test.ts adds tests for inline comments, quoted values followed by a comment, the export prefix, multi-line and \n values, $VAR staying unexpanded, and a file that starts with a byte order mark.

Choices to check

• Lines without = are now skipped, as in .env loading, instead of failing. The found names are still listed before the confirm prompt.
• Secrets are listed in name order, not file order, because parseEnv returns keys sorted.

🤖 Generated with Claude Code

[Brooooooklyn]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T08:07:04.191277Z	8307197	New commits

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 31aefeb594

ℹ️ 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".

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://fix-secret-sync-dotenv-void-cloud.voidzero-docs.workers.dev (commit 8307197)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://d764079e-void-cloud.voidzero-docs.workers.dev	8307197	2026-10-27T08:06:56.717Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://f35626b3-void-cloud.voidzero-docs.workers.dev	69db2fd	2026-10-27T07:55:17.158Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://743a9b03-void-cloud.voidzero-docs.workers.dev	31aefeb	2026-10-27T07:31:21.922Z	Visit the dashboard ↗

[chatgpt-codex-connector]

💡 Codex Review

void/packages/void/src/auth/config.ts

Lines 104 to 105 in 69db2fd

	const config = await resolveConfig({ root, mode: 'development', logLevel: 'silent' }, 'serve');
	return viteAuthConfigImporter(root, config.mode, config.resolve)(path);

Keep void prepare independent of application plugin startup

For projects with an auth.ts, prepareProject() now calls this importer, which evaluates vite.config and executes the application's plugin configuration hooks. This violates the package's explicit invariant that void prepare boots no Vite. It also introduces concrete side effects beyond preparing types: constructing Void's routing plugin rewrites .void/entry.ts with its initial entry, even though this configuration-only invocation never reaches buildStart to finish generating the application. Preserve auth import resolution without bootstrapping the full application plugin graph during preparation.

AGENTS.md reference: packages/void/AGENTS.md:L169-L169

ℹ️ 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".

[Brooooooklyn]

Fixed in 106d132 on #611, which this PR is stacked on. void prepare, void gen and void db generate no longer load the app's vite.config: auth.ts is evaluated with Vite's runnerImport (no config file), using tsconfig paths and Void's own @schema alias. The prepare test now has a vite.config that writes a marker file and checks it is never written.