Skip to content

[codex] add windows smoke test workflow#2

Draft
jniplig wants to merge 2 commits intoZiforge:mainfrom
jniplig:codex/windows-smoke-validation
Draft

[codex] add windows smoke test workflow#2
jniplig wants to merge 2 commits intoZiforge:mainfrom
jniplig:codex/windows-smoke-validation

Conversation

@jniplig
Copy link
Copy Markdown

@jniplig jniplig commented Apr 5, 2026

What changed

  • added a minimal read-only TCP smoke test client
  • added a Windows deploy script for installing ClaudeMCP_Remote into the validated Ableton script path
  • added a Windows smoke-test wrapper for listener checks and raw request/response capture
  • documented the validated ASUS/Windows runtime behavior and smoke-test workflow

Why

The repo looked promising but early-stage, so this change stays additive and avoids touching the core Remote Script while establishing a repeatable runtime validation loop.

Validated behavior

  • Ableton Live 12.3.6 loaded ClaudeMCP_Remote without obvious startup errors
  • the script exposed a listener on 127.0.0.1:9004 from the Windows side
  • read-only actions ping, health_check, and get_session_info returned valid JSON responses
  • raw request/response output was captured successfully

Notes

  • no changes were made to ClaudeMCP_Remote/init.py or ClaudeMCP_Remote/liveapi_tools.py
  • this machine required installation into the built-in ProgramData MIDI Remote Scripts directory and explicit Control Surface selection
  • WSL-side socket checks did not reliably reflect the Windows Ableton listener, so runtime validation docs now direct users to Windows-native checks

Checks

  • python3 -m py_compile scripts/poc/smoke_test_client.py
  • Windows-native smoke test against a live Ableton session on the ASUS machine

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