feat(amp): add ZERO-294 Amp adapter#43
Closed
spencercharest wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
Folded into #63 as a matrix entry ( |
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.
Summary
plugins/zero-ampwith an Amp TypeScript plugin and an Agent Skill MCP overlay.scripts/build-amp.shto assemble.amp/plugins/zero.ts,.agents/skills/zero/SKILL.md, embedded.agents/skills/zero/mcp.json, and the runner/context helpers intodist/zero-amp.guides/amp.mdand links it from the README Install Zero list.1.4.0viamake minor.Ticket
ZERO-302 under ZERO-294.
Official references checked
amp plugins show-docsInstall/update surfaces
Project install:
git clone https://github.com/officialzeroxyz/zero-plugins.git cd zero-plugins ./scripts/build-amp.sh cp -R dist/zero-amp/. /path/to/your/workspace/Global install:
Update is
git pull, rebuild, and repeat the copy step.Verification
./scripts/build-amp.sh./scripts/build-amp.sh --tar /tmp/zero-amp.tar.gzmake version->1.4.0jq .on all Amp JSON files.@ampcode/plugin:git diff --checkguides/agent-install.mdis not modified.Docker install/load/hook smoke plus copied-auth Zero loop:
Observed:
~/.zerowas copied into Docker from the host. Nozero reviewwas submitted, per the ZERO-294 test instructions.E2E status
Draft because a full Amp-agent-driven Zero capability call still needs an authenticated Amp account/API key. In this environment:
~/zeroclick/envdoes not containAMP_API_KEY.amp plugins list/amp plugins execattempted to load global plugins and failed without an Amp service connection:failed to load global plugins. Unable to connect to https://ampcode.com/.Verified: current Amp CLI install, package assembly, embedded MCP skill layout, TypeScript plugin compile, runner helper provisioning, copied
~/.zeroauth inside Docker, Zero search/get/fetch, and returned CDN file verification.Proposed
guides/agent-install.mdnotesDo not apply this text in this PR. This is the proposed runbook section to fold into
guides/agent-install.mdlater.Claude-style plugin compatibility and simpler install option
Full Claude Code plugin package support: No. Amp has its own TypeScript/plugin and repo config model. It reads Claude-compatible skills, so the Zero skill body can be reused, but Amp does not install Claude Code
.claude-pluginpackages as its native plugin artifact.What this means for users:
End users should not build the adapter. The consumer path should be a published package or a prebuilt repo-template artifact.
Preferred full-integration path once published:
Verify exact Amp plugin command syntax before making this ready.
If the TypeScript adapter is not worth maintaining, a simpler option is to place the existing Zero skill under
.claude/skills/zeroor Amp's native skill path and embed the Zero MCP config in the skill. That is likely much lower maintenance, but it drops plugin hooks.GitHub Releases / no-build install check
Result: No native Gemini-style GitHub Release install path found. Amp's integration is repo/package oriented and can reuse skills/MCP, but I did not verify an Amp command that installs plugin release assets directly from GitHub Releases.
Best no-build consumer path should be one of:
if Amp supports package installs for this plugin shape, or a prebuilt repo-template archive users extract into their project.
A GitHub Release asset can remove the need to run
scripts/build-amp.sh, but unless Amp gains/has release-asset install semantics it remains a manual download/extract artifact, not a Gemini-style one-command install.