/amplihack:remote --region {region} --vm-size {size} auto "{task}"
If no region mentioned, omit --region (uses azlin default)
Execute the command
using the SlashCommand tool
Guide the user
on next steps:
Results will be in
~/.amplihack/.claude/runtime/logs/remote/
Git branches in
remote-exec/
namespace
How to view logs and integrate changes
Examples
Example 1: Simple with Region
User
"Run this analysis remotely on an eastus VM"
Your Response
:
I'll execute this analysis on a remote Azure VM in eastus.
Detected:
- Task: analysis work
- Region: eastus
- Size: s (small - suitable for analysis)
Executing: /amplihack:remote --region eastus --vm-size s auto "analysis work"
Then use SlashCommand tool to execute it.
Example 2: Large Refactoring
User
"I need to offload this comprehensive refactoring to Azure, use westus2"
Your Response
:
I'll execute this comprehensive refactoring on a remote Azure VM in westus2.
Detected:
- Task: comprehensive refactoring
- Region: westus2
- Size: l (large - for comprehensive work)
Executing: /amplihack:remote --region westus2 --vm-size l auto "comprehensive refactoring"
Example 3: No Region Specified
User
"Run this remotely"
Your Response
:
I'll execute this task on a remote Azure VM using your default region.
Detected:
- Task: [extract from context]
- Region: default (from azlin config)
- Size: m (medium - standard)
Executing: /amplihack:remote --vm-size m auto "[task]"
Result Integration
After execution completes, guide the user:
Remote execution complete!
Results:
- Logs: .claude/runtime/logs/remote/
- Branches: Check git branch -r | grep remote-exec
- Integration: Review changes and merge if ready
To view logs:
cat .claude/runtime/logs/remote/remote-exec-*.log
To merge remote changes:
git fetch
git merge remote-exec/main
Error Handling
If the command fails, explain common issues:
Secrets Detected
:
"Remote execution blocked - secrets found in repository. Please remove hardcoded secrets and use .env files instead."
Azlin Not Configured
:
"Azlin is not configured. Please run:
azlin configure
"
Timeout
:
"Task timed out. The VM has been preserved for inspection. Use
azlin connect
to investigate."
Best Practices
Remind users:
Keep git state clean before remote execution
Use
.env
for secrets (never hardcode)
Monitor Azure costs with
azlin list
Clean up VMs after debugging with
azlin kill
Token Budget
Core instructions: ~1,200 tokens
Examples and guidance: ~400 tokens
Total: ~1,600 tokens (well under 2,000 limit)
See Also
/amplihack:remote
- Direct command interface
Azlin documentation:
https://github.com/rysweet/azlin
Remote execution module:
~/.amplihack/.claude/tools/amplihack/remote/README.md