Skip to content

feat(engines): add privacycode as a supported engine - #74

Merged
ralyodio merged 1 commit into
mainfrom
feat/privacycode-engine
Jul 28, 2026
Merged

feat(engines): add privacycode as a supported engine#74
ralyodio merged 1 commit into
mainfrom
feat/privacycode-engine

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Registers privacycode alongside opencode/claude/codex/gemini/aider so moshcode engines, moshcode install privacycode, moshcode agents privacycode and the headless ai() shortcut all know about it.

Install one-liner used:

curl -fsSL https://getprivacycode.com/install | sh

Changes

  • src/engines.mjs — new privacycode entry (bin: privacycode, agentArgs: ["--auto"], agentsView: ["agent","list"], upgrade: privacycode upgrade); aliases pc / privacy / getprivacycode; headless ai() mapping (privacycode run <prompt>); added to the pickAiEngine fallback order.
  • src/mcp.mjs — added to MCP_ENGINES, sharing opencode's mcp add --url case (privacycode is an opencode derivative, so it inherits the remote-servers-only limitation).
  • README.md, test/engines.test.mjs — engine lists / expectations updated.

Known gap (not a blocker for this PR)

https://getprivacycode.com/install is currently still the unmodified opencode installer: APP=opencode, installs into $HOME/.opencode/bin, and pulls from github.com/anomalyco/opencode/releases. It therefore drops a binary named opencode, not privacycode, and profullstack/getprivacycode has no releases yet.

So moshcode install privacycode runs fine but the engine keeps reporting not-installed until getprivacycode ships its own releases and rebrands the installer. Registering bin: "privacycode" (the name in packages/privacycode/package.json) is the correct target state — pointing it at opencode would collide with the existing opencode engine.

Testing

  • node --test test/engines.test.mjs test/mcp.test.mjs → 33/33 pass.
  • Full npm test has one failure, upgrade tools selects installed workflow tools without self or engines, which reproduces on clean main (verified by stashing) — pre-existing and unrelated.
  • moshcode engines now lists ○ privacycode.

🤖 Generated with Claude Code

Registers privacycode alongside opencode/claude/codex/gemini/aider so
`moshcode engines`, `moshcode install privacycode`, `moshcode agents
privacycode` and the headless ai() shortcut all know about it. Installed
via its official one-liner:

  curl -fsSL https://getprivacycode.com/install | sh

privacycode is an opencode derivative, so it inherits opencode's flag
surface (--auto, `agent list`, `run <prompt>`) and shares opencode's
`mcp add --url` case — including the remote-servers-only limitation.

Note: getprivacycode.com/install currently still drops the upstream
`opencode` binary into ~/.opencode/bin, so the engine will report
not-installed until getprivacycode ships its own releases and rebrands
the installer. Registering bin "privacycode" (the name in its
package.json) is the correct target state; pointing it at "opencode"
would collide with the existing opencode engine.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.

@ralyodio
ralyodio merged commit eceb4f0 into main Jul 28, 2026
3 checks passed
@ralyodio
ralyodio deleted the feat/privacycode-engine branch July 28, 2026 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant