Repository navigation
Conversation
Laptop Tailscale is already up; this is the leftover machine checklist so an agent on the Mini can finish join, SSH, install.sh, and auth without copying tokens. Co-authored-by: Cursor <cursoragent@cursor.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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[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: f8f951d8dc
ℹ️ 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".
| ```bash | ||
| mkdir -p ~/.cstack | ||
| if [ ! -d ~/.cstack/src/.git ]; then | ||
| git clone git@github.com:chasehuh/cstack.git ~/.cstack/src |
There was a problem hiding this comment.
On the documented fresh-Mini path, the only key installed before this command is the laptop's public key in the Mini's authorized_keys; that permits inbound laptop-to-Mini SSH but gives the Mini no private key for outbound GitHub authentication. Consequently, this git@github.com clone can fail before the GitHub login/key setup in §5 is ever reached, blocking install.sh; move the Mini's GitHub SSH-key setup earlier or clone this public repository over HTTPS.
Useful? React with 👍 / 👎.
| | Tool | Why | Command (typical) | | ||
| | --- | --- | --- | | ||
| | GitHub `gh` | issues, `gh pr`, CI | `gh auth login` (same `sumelabs` / `chasehuh` access as laptop) | | ||
| | SSH to GitHub | `cstack-clone`, `gt submit` | `gh auth setup-git` and/or Mini’s own `~/.ssh` key in GitHub | |
There was a problem hiding this comment.
If the operator follows gh auth setup-git as the advertised alternative, the later SSH acceptance check and cstack-clone still fail because gh auth setup-git --help states that it configures GitHub CLI as a Git credential helper, which applies to HTTP(S) credentials and does not create or register an SSH key. Since both git ls-remote git@github.com:sumelabs/sume-com.git and the default CSTACK_GIT_URL use SSH, require generation and registration of a Mini-owned SSH key rather than saying these options are interchangeable.
Useful? React with 👍 / 👎.
| | SSH to GitHub | `cstack-clone`, `gt submit` | `gh auth setup-git` and/or Mini’s own `~/.ssh` key in GitHub | | ||
| | Graphite `gt` | sume-com PRs | `gt auth` / `gt config` | | ||
| | Claude Code / tokenmaxxing | Opus / Fable | tokenmaxxing init **on Mini** | | ||
| | Codex | Astra | Codex login **on Mini** | |
There was a problem hiding this comment.
On a Mini with a directly installed Codex CLI, the suggested bare “Codex login” and subsequent command -v codex check can pass without creating the required tokenmaxxing Codex pool, causing workers to use the wrong credential/account path. The setup should run tokenmaxxing init --codex (or add --codex) and verify that codex resolves to ~/.config/tokenmaxxing/bin/codex, as required by this desk's Codex transport.
AGENTS.md reference: AGENTS.md:L52-L52
Useful? React with 👍 / 👎.
1 participant
Summary
docs/MINI-REMAINING.md— ordered Mini-side checklist (Tailscale, Remote Login, laptop pubkey,install.sh, per-host logins, report-back strings).MINI-WORKER-HOST.mdat that page and cstack#12.Test plan
gh~/.cstack/srcthen opendocs/MINI-REMAINING.mdMade with Cursor