Repository navigation
Conversation
Checked against origin/main code. Docs only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
johncwaters
left a comment
There was a problem hiding this comment.
Note
Automated review. Not written by a human.
| POSTHOG_GATEWAY_TOKEN=phs_... | ||
| # Gateway service key for model calls: a phs_ project secret key with the llm_gateway:read scope. | ||
| # It's in 1Password. Keep the op:// reference and run with `op run --env-file .env -- pnpm ...`. | ||
| POSTHOG_GATEWAY_TOKEN=op://<vault>/<item>/credential |
There was a problem hiding this comment.
Note
Automated review. Not written by a human.
This placeholder isn't valid shell. Bash parses <vault> and <item> as redirections, so source .env fails with vault: No such file or directory and returns non-zero. Every phrocs pane that runs source .env && ... (context-mill, mcp-inspector, wizard-build, wizard-build-dev, playground) then won't start after a fresh cp .env.example .env. Real op:// references with spaces in the item name break the same way.
Fix: quote it and drop the angle brackets, e.g. POSTHOG_GATEWAY_TOKEN="op://vault/item/credential".
| | `POSTHOG_REGION` | No | PostHog region (`us` or `eu`). Defaults to `us`. Can also be set via `--region` flag or workflow input. | | ||
| | `POSTHOG_PERSONAL_API_KEY` | For development | PostHog personal API key (`phx_`). Gives the wizard PostHog API and MCP access in CI mode, `--e2e` and `mcp-stub:record`. | | ||
| | `POSTHOG_WIZARD_PROJECT_ID` | For `--e2e` | The project the personal API key is scoped to. Used by `pnpm wizard-ci --e2e` (or pass `--project-id`) and `pnpm wizard-ci-snapshots`. | | ||
| | `POSTHOG_GATEWAY_TOKEN` | For development | The gateway service key for model calls: a `phs_` project secret key with the `llm_gateway:read` scope. It's in 1Password. Set it to `op://<vault>/<item>/credential` and run with `op run --env-file .env -- pnpm ...`. The PR evaluator and `pnpm wizard-ci --e2e` fail without it. | |
There was a problem hiding this comment.
Note
Automated review. Not written by a human.
If .env keeps the unresolved op:// reference, the phrocs panes that need the token (wizard-ci-run --evaluate, wizard-ci-evaluate-pr, wizard-ci-snapshots) load it through env_file without op run. They get the literal op://... string, which passes the non-empty checks in services/pr-evaluator/evaluator.ts and services/wizard-ci/e2e.ts and goes to the gateway as the token, so you get a gateway auth error instead of the clear "no gateway token" message.
Fix: document starting phrocs as op run --env-file .env -- phrocs, or say these panes need a resolved key.
Problem
The README's local stack steps don't produce a working wizard run:
./bin/startplus--local-posthoghas no gateway, and the local LLM gateway section is stale.Changes
hogli dev:apply product_analytics --include ai-gateway,hogli up, theWIZARD_GATEWAY_*mint settings, phrocs,pnpm try ... --local-posthog --local-context-mill. Replaces the tsdownNODE_ENVand :3308 instructionsservices/mcp/.env, not.dev.varssstart,xstop), picker labels,apps/manifest.jsonregistry, env table (POSTHOG_GATEWAY_TOKENand others),--regionscope, workflowappinput paths, owners table synced to CODEOWNERSPOSTHOG_PERSONAL_API_KEY(phx_, MCP access) andPOSTHOG_GATEWAY_TOKEN(phs_gateway service key, anop://reference to 1Password run throughop run)..env.exampleupdated to matchTest plan
Docs only. The local flow matches a verified end-to-end run on 2026-09-24. Other claims were checked against origin/main of the workbench, the wizard and posthog.
🤖 Generated with Claude Code