Skip to content

Releases: proofpoint/amap-release

2026-10-28

Choose a tag to compare

@rappdw rappdw released this 29 Oct 00:54

AMAP collective release amap-2026-10-28: Codex unified conversations. A Codex agent can take human interaction and incoming AMAP work in one persistent conversation. Based on amap-2026-10-10; only the Codex connector and the Sandy deployment change. Closes #1.

Repository Commit Change
amap-connector-claude 3a20c28080ad560a55e202ea59596c1ae1733661 Unchanged
amap-connector-codex e10eb2cf22a1056d1506938ef0669bfde582ff75 Updated
amap-deploy-sandy 3b605d028ad312442e9569b9a9e7fcfe7f4c9efb Updated
amap-router-local 972cb7096bf4110811cbafc20a6a8019d7408576 Unchanged

Each component repository has a matching amap-2026-10-28 tag. The manifest records the tag objects, the CI and installed-payload validation, and the evidence for each required behavior.

Install

curl -fsSL https://raw.githubusercontent.com/proofpoint/amap-release/main/install.sh | bash

This installs sandy if it's missing, puts the components at this release's tags under ~/amap, installs the feature, and starts the router.

Unified mode is an explicit choice. Activate it with install --codex-mode unified. The one-command installer makes that choice by default, but only on a host with no Codex sandboxes; set AMAP_CODEX_MODE=separate to opt out. Unified mode applies to newly created Codex-served sandboxes only. Without it, hosts keep separate mode. Installing this release never migrates or erases existing Codex state. Existing Codex sandboxes are held until the operator recreates them by the documented procedure. Adoption of an existing saved conversation isn't supported in this release. See Codex unified conversations.

The evidence is synthetic: real Codex 0.164.0 with disposable homes and local inference. It doesn't establish acceptance on a target host, so run the runbook's pilot first.

Offline backup amap-2026-10-28-backup.tar.gz (stored separately), SHA-256: d78dfeb6fb6fd12198ddb5abdda2c78b4fa433be5cd6020ad2bb22b1e3f25c97. Restore-tested.

Re-cut on October 28. The deployment pin moved from e4e5362 to its child 3b605d0 (amap-deploy-sandy#114). That commit fixes install.sh failing silently under a umask of 002 and changes nothing else. amap-deploy-sandy's amap-2026-10-28 tag and this repository's 2026-10-28 tag were re-pointed, and the backup was rebuilt. The other component tags are unchanged. If you fetched the tags earlier, run git fetch --tags --force.

2026-10-10

Choose a tag to compare

@rappdw rappdw released this 29 Oct 00:25
67cd929

AMAP collective release amap-2026-10-10. The manifest pins these component commits. Each component repository has a matching amap-2026-10-10 tag.

Repository Commit
amap-connector-claude 3a20c28080ad560a55e202ea59596c1ae1733661
amap-connector-codex 87347ad49837563678f50c4119248ecd2dda048d
amap-deploy-sandy ef93e4f179ebe13470e11e982fdf465f709f0530
amap-router-local 972cb7096bf4110811cbafc20a6a8019d7408576

Offline backup archive SHA-256: 7fa7de7adb09f0d10fa88becc0c939fd5b3c105c60e4f68e9efd2a7b0ade0ef5 (amap-2026-10-10-backup.tar.gz, stored separately).

See the README for checkout and restore instructions.