docs: Grok Build onboard path (Kimi-ready)#48
Conversation
Capture day-one lessons: nudge_mode none is a footgun, per-agent notify files, tmux path vs Grok-native 2m self-schedule, example config without secrets. README section + docs/grok-build.md + config/grok.example.json.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
![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: 61ea2637e9
ℹ️ 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".
| ### A. IAK path (poller + tmux nudge) | ||
|
|
||
| ```bash | ||
| cp config/grok.example.json config/grok.json |
There was a problem hiding this comment.
For users following this onboarding from an npm-installed copy, this first command fails because config/grok.example.json is not shipped: I checked npm pack --dry-run --json and the package includes docs/grok-build.md but no config/* files, matching the existing .gitignore rule config/*.json and no npm override. Either explicitly include this example in the package or put it somewhere that is published, otherwise the new Grok setup path is broken outside a git checkout.
Useful? React with 👍 / 👎.
1 participant
Summary
check room.config/grok.example.json(no secrets),docs/grok-build.md, and a README "Grok Build" section.Key lessons
nudge_mode: "none"is the footgun that made Grok look dead./loop 2mworks outside tmux.Test plan