Show current Campus work and GitHub Issue - #36
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: 0cfea2a9bd
ℹ️ 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".
| write_method = getattr(self, "command", "").upper() in { | ||
| "POST", | ||
| "PUT", | ||
| "PATCH", | ||
| "DELETE", | ||
| } | ||
| expected = _dashboard_run_token(create_if_missing=write_method) |
There was a problem hiding this comment.
On a fresh deployment or after the token file is removed, every GET now calls _dashboard_run_token(create_if_missing=False), while the deployment script never creates the file and mm-command-center-auth immediately tries to read it. The public UI also disables its write action until a token is supplied, so the documented authorization flow cannot bootstrap without first issuing an undocumented unauthenticated POST solely to create the token; provision it during deployment/startup instead.
Useful? React with 👍 / 👎.
| const token = window.localStorage | ||
| .getItem('command-center.jarvis-run-token') | ||
| ?.trim(); | ||
| if (token) headers['X-Dashboard-Run-Token'] = token; |
There was a problem hiding this comment.
When the supported dashboard is opened from file://, PIXEL_AGENTS_BASE loads this script in an iframe from https://command.meshly.fr, but the saved run token belongs to the parent file origin. Reading window.localStorage here therefore cannot see that token, so every Campus refresh receives the anonymous projection and the new summary/Issue rows remain unavailable to the owner; explicitly pass the token from the parent to the iframe or perform the authenticated request in the parent.
Useful? React with 👍 / 👎.
1 participant
Closes #34
Summary
Safety
Verification
Note
Live browser rendering was unavailable in this session; responsive and DOM behavior is covered by deterministic Campus tests and static review.