Repository navigation
feat: cogos-cloud-node plugin (CogOS node in a Cloud env, phone-friendly) - #32
Merged
Merged
Conversation
… (phone-friendly) Thin convenience plugin + operator-template-repo architecture (repo's SessionStart hook owns bootstrap; data-export seed; no operator data). Verified: falsifiable local harness + fresh-env deploy sim PASS (file assertions; broken input fails loudly). Ships method only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
cogos-cloud-node: stand up a CogOS node in a Claude Code Cloud environment, usable from a phone.Architecture (after 3 review rounds, R2 invalidated an earlier inert-plugin design):
~/.cogoswhen attached to a Cloud env (no UI paste, no plugin-inert problem).Verified (real command output, file assertions not exit codes):
Ships method only — no operator data, no credentials (secrets come from the env's Network-secrets slot, the operator's own PAT).
Honest boundary: the Cloud-env/secrets UI setup (steps 3-6 in the checklist) and the true phone end-to-end install need a real Cloud session — not verifiable in a container; flagged, not faked.