Skip to content

fix: AMP mesh routing + upstream v0.1.3 fixes#315

Merged
jpelaez-23blocks merged 1 commit intomainfrom
fix/amp-mesh-routing-v0.26.4
Mar 25, 2026
Merged

fix: AMP mesh routing + upstream v0.1.3 fixes#315
jpelaez-23blocks merged 1 commit intomainfrom
fix/amp-mesh-routing-v0.26.4

Conversation

@jpelaez-23blocks
Copy link
Copy Markdown
Contributor

Summary

Rebuilt plugin from upstream agentmessaging/claude-plugin main with 3 critical fixes:

  • amp-send.sh: Check config.json before filesystem delivery — fixes mesh routing broken after message migration created local directories for remote agents
  • amp-fetch.sh: Add missing /v1/ prefix to fetch and acknowledge URLs (was causing 404s against Crabmail)
  • amp-helper.sh: generate_message_id() uses seconds-precision timestamps per AMP spec

Root cause

install-plugin.sh message migration distributed 1845 messages to per-agent directories, creating ~/.agent-messaging/agents/<name>/messages/ for ALL agents — including remote ones. amp-send.sh checked if [ -d RECIPIENT_AMP_DIR ] which matched these migration dirs, routing everything via filesystem instead of mesh.

Test plan

  • amp-send.sh to remote agent routes via mesh (not local filesystem)
  • Local agents still get filesystem delivery
  • yarn test — 545 pass
  • yarn build — clean

🤖 Generated with Claude Code

- amp-send.sh: check config.json before filesystem delivery (fixes mesh
  routing broken after message migration created local dirs for remote agents)
- amp-fetch.sh: add missing /v1/ prefix to fetch/acknowledge URLs
- amp-helper.sh: seconds-precision timestamps per AMP spec

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jpelaez-23blocks jpelaez-23blocks merged commit 6a223ec into main Mar 25, 2026
3 checks passed
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