Set up with your agent

Set up Assemble VMs in this project. Retrieve and read the entire agent skill at https://docs.assemble.ai/skill.md, then follow its setup and verification instructions. Read the complete Markdown, including installation, persistence, and cleanup. If you cannot retrieve it, tell me and use a full copy I provide before implementing the SDK integration. Do not substitute a summary or guess a registry package.

Inspect this project's existing server-side structure and add the smallest useful SDK integration plus a runnable first-session example. Use the local Assemble checkout or the package archives I provide; the SDK is not published to npm yet. Configure ASSEMBLE_BASE_URL=https://assemble-vms-api.fly.dev unless I supply a different service URL. Read ASSEMBLE_BASE_URL and ASSEMBLE_API_KEY only from the server or local development environment. Never print the key, put it in browser code, or ask me to paste it into this conversation.

Use client.sessions.open to create or reopen a dedicated setup session. Write a small verification file, execute a command that reads it, inspect stdout and the final exit code, and verify the exact contents through the file API. Pause the session, open the same name again, and verify both the session ID and file contents were retained. Finish with the session paused. Keep the session and its files; delete them only if I explicitly request cleanup later.

Use the remote-harness integration as the starting point; a model call is not needed to verify the VM. Run the available checks when the environment is ready. If access or credentials are missing, finish the code and tell me exactly which non-secret setup step remains. Report the files changed, command to run, checks that actually passed, and retained session ID. Do not claim unrun checks passed.

Implement a basic Assemble VMs integration in this project. Retrieve and read all of the agent skill at https://docs.assemble.ai/skill.md before editing. Treat that complete Markdown file as the canonical SDK setup and verification guide, including persistence and cleanup. If the URL cannot be read, tell me and use a full copy I provide before implementing the SDK integration. Use the local checkout or package archives I supply; npm packages are not yet published. Hosted access requires an operator-issued product key.

Follow this project's existing server-side conventions. Add a small SDK client module and a runnable first-session example. Set ASSEMBLE_BASE_URL=https://assemble-vms-api.fly.dev unless I supply a different service URL. Read ASSEMBLE_BASE_URL and ASSEMBLE_API_KEY through the server or local development environment. Keep the key out of prompts, logs, committed files, and client-side bundles. If a value is missing, tell me its variable name without asking me to send its secret value.

Verify a dedicated session using client.sessions.open: write a small file, run a command that reads it, stream stdout/stderr, check completed state and exit code zero, and compare the file API response with the bytes written. Pause and reopen the same session name. Confirm the ID and file contents still match, then leave the session paused. Retain this session until I explicitly ask for deletion.

Start with remote file and command tools; no model-provider key or agent run is required. Finish the integration even if a missing service or key blocks the live check. In your handoff, list the changed files, exact run command, verification results, retained session ID if created, and any remaining setup step. Distinguish checks you ran from checks that are still pending.