Skip to content

Feature/tg customer#5

Open
zyjblockchain wants to merge 5 commits intomainfrom
feature/tg-customer
Open

Feature/tg customer#5
zyjblockchain wants to merge 5 commits intomainfrom
feature/tg-customer

Conversation

@zyjblockchain
Copy link
Copy Markdown
Collaborator

No description provided.

cryptowizard0 and others added 5 commits April 9, 2026 17:58
Introduce a new Claude runtime implementation and related build/bootstrap artifacts. Adds runtime/claudecode (CLI wrapper, checkpoint/restore, env/config parsing, retries, and unit tests) and wires it into runtime selection. Add Dockerfile.claude, rename Dockerfile -> Dockerfile.openclaw, add bootstrap hooks (bootstrap/claude.sh, bootstrap/openclaw.sh) and dedicated build helpers (docker_build_claude.sh, docker_build_openclaw.sh). Update .env_example, AGENTS.md and readme.md with new env vars, build/run guidance and scripts; remove obsolete docker_build.sh and sandbox-profile.sh. Small server/tests/scripts tweaks and permission/entrypoint adjustments for the new runtime images.
Copy link
Copy Markdown
Owner

@cryptowizard0 cryptowizard0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. The overall direction is clear: split image flavors, add runtime-specific bootstrap hooks, and introduce Claude / TelegramCustomer runtimes. I found two merge-blocking issues that should be fixed before this can be reviewed as a runnable change.

Also please clarify whether telegramcustomer is intentionally spawn/checkpoint-only. Right now /vmm/apply always returns telegramcustomer apply is not implemented, while the PR adds smoke coverage only for spawn/checkpoint/restore. If callers are expected to use the normal VMM apply path with this runtime, that behavior still needs implementation or documentation as an explicit non-goal.

I did not see CI/status checks on the PR. After the fixes, please run at least go test ./..., ./docker_build_openclaw.sh, ./docker_build_claude.sh, and the TelegramCustomer image build/smoke path in a clean checkout.

Comment thread go.mod
rsc.io/tmplfunc v0.0.3 // indirect
)

replace github.com/xingj404-lab/claude-gw => /Users/sandyzhou/codex-project/claude-gw
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This committed replace points at a developer-local absolute path, so a clean checkout cannot resolve github.com/xingj404-lab/claude-gw. It also affects the non-Telegram builds because go.mod is copied before the Dockerfile-specific go mod edit steps, so go test ./..., Dockerfile.openclaw, and Dockerfile.claude can fail on any machine that does not have /Users/sandyzhou/codex-project/claude-gw. Please remove this from committed go.mod and keep the local override limited to the TelegramCustomer Docker build context or publish/pin a normal module version.


COPY --from=builder /app/main /app/main
COPY start-vmdocker-agent.sh /usr/local/bin/start-vmdocker-agent.sh
COPY bootstrap/telegramcustomer.sh /usr/local/lib/vmdocker-agent/bootstrap/telegramcustomer.sh
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This copies bootstrap/telegramcustomer.sh, but that file is not present in the PR. The changed-file list only includes bootstrap/claude.sh and bootstrap/openclaw.sh, so the TelegramCustomer image build will fail at this COPY step. Please add the hook file or adjust the Dockerfile/tests to match the files actually committed.

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.

3 participants