OpenMaple v0.2.1 launch: local Docker managed agents with one setup script

[dragonforce2010]

2026-06-22 update: one-command local Docker setup

OpenMaple v0.2.1 is live: https://github.com/dragonforce2010/openmaple/releases/tag/v0.2.1

Post-release update: PR #58 has also landed on main, with HD public proof assets for the local-Docker path: 5120x2880 real UI screenshots plus a 2560x1440 walkthrough covering setup, smoke checks, workspace settings, runtime pool drawer, sandbox pool drawer, sessions, and quickstart UI:

#58

The latest main checks for CI, GitHub Pages, and Cloud Deploy are green.

Fastest evaluation path:

./scripts/setup-local-docker.sh
npm run smoke:local -- --base http://127.0.0.1:27951

Then open:

Web console: http://127.0.0.1:8080/
Local login:  http://127.0.0.1:8080/?dev_login=1
API health:   http://127.0.0.1:27951/health

You can also start from GitHub Codespaces: https://codespaces.new/dragonforce2010/openmaple?quickstart=1

The default local path starts separate web, api, and mysql services, local dev login, local Docker runtime pools, and local Docker sandbox pools. It does not need E2B, veFaaS, or OAuth credentials; model keys are only needed for real model-backed agent loops.

What is in the repo today:

• React console and Express API
• Agent, environment, session, vault, runtime pool, sandbox pool, and deployment resources
• Session event log for messages, tool calls, artifacts, failures, and runtime metadata
• Local Docker setup script with local MySQL, dev login, local Docker runtime pools, and local Docker sandbox pools
• Provider boundaries for runtime, sandbox, storage, model access, and cloud identity
• Node SDK and CLI packages
• Public-safe real console screenshots, website, YouTube tour, and release notes
• Post-merge HD local-Docker UI evidence for setup, runtime/sandbox settings, pool drawers, sessions, and quickstart

Links:

• Repo: https://github.com/dragonforce2010/openmaple
• Site: https://dragonforce2010.github.io/openmaple/
• Release: https://github.com/dragonforce2010/openmaple/releases/tag/v0.2.1
• Product tour: https://dragonforce2010.github.io/openmaple/#tour
• Local Docker walkthrough: https://dragonforce2010.github.io/openmaple/#local-docker-tour
• YouTube: https://www.youtube.com/watch?v=zYhgkFomZ7M
• Chinese note: https://www.xiaohongshu.com/explore/6a38293b000000001101aee8?xsec_token=YBXBpTxQf4qB3MzSz-YcjayfnABQegjIwwo5jabda7qM0%3D&xsec_source=pc_creatormng
• Evaluation guide: https://github.com/dragonforce2010/openmaple/blob/main/EVALUATION.md
• Provider readiness: https://github.com/dragonforce2010/openmaple/blob/main/PROVIDER_READINESS.md
• Managed Agents reference idea: https://www.anthropic.com/engineering/managed-agents

OpenMaple is not an official Anthropic product. It is an open implementation of the same platform idea: split AgentRuntime from SandboxRuntime, persist session state, isolate credentials, and keep provider layers replaceable.

Feedback wanted:

1. Does the current Agent -> Environment -> Session -> Event Log model match how your team would build an internal agent platform?
2. Does the local Docker path lower the trial cost enough for an internal spike?
3. Which provider adapter matters most next: AWS Lambda, Alibaba FC, Vercel Sandbox, S3/GCS storage, or another path?
4. What is the first missing proof you would need before trying this inside an engineering team?

If this direction is useful, star the repo so I can prioritize public docs, examples, and provider adapters around real user interest.

[dragonforce2010]

Contributor entry points added for anyone who wants to help shape the provider roadmap:

• Improve minimal SDK example with expected output #34 Improve the minimal SDK example with expected output
• Add AWS Lambda AgentRuntime adapter spike #35 Add an AWS Lambda AgentRuntime adapter spike
• Add Vercel Sandbox provider research spike #36 Add a Vercel Sandbox provider research spike
• Define S3 and GCS artifact storage provider boundary #37 Define the S3 and GCS artifact storage provider boundary

These are intentionally scoped as evaluation and adapter-boundary work, not broad production-ready claims. If you are evaluating OpenMaple for an internal platform, comments on which provider matters first are more useful than generic feature requests.

[dragonforce2010]

New public product tour is live on the website, YouTube, and README: https://dragonforce2010.github.io/openmaple/#tour

YouTube: https://www.youtube.com/watch?v=zYhgkFomZ7M
Direct MP4: https://dragonforce2010.github.io/openmaple/assets/videos/openmaple-platform-tour.mp4

Local evaluation now has a self-contained Docker Compose path: console, API, MySQL, local dev login, local Docker runtime pools, and local Docker sandbox pools. E2B and veFaaS credentials are not required for the default local path; model keys are only needed for real model-backed loops.

The tour is built from the running console and existing end-to-end launch screenshots: agent creation, cited sandbox sessions, vaults, CLI, SDK, skills, deployments, and observability.