Over the past week, I have been working on my DevSandbox (https://github.com/jprogramista/devsandbox) to make it even easier to use. My main assumption was that it should be fully remote, with minimal reliance on the CLI.
To achieve this, I used Slack and n8n, tools I had already worked with successfully in AIword (which I still actively use for news). Slack is responsible for creating tasks for Claude and monitoring their progress. n8n triggers tasks directly on the DevSandbox. Once a task is completed, Claude creates a pull request on GitHub.
The pull request can then be reviewed, approved, and merged. After that, Jenkins runs the build, executes tests, and performs the deployment. The entire process is supervised by scripts stored in the DevSandbox repository, supported by very lightweight control scripts in n8n and Jenkins configuration.
From my perspective, the whole system operates fully automatically. For a short period, I even ran this solution without pull requests, but I considered that too risky – there was always a chance that Claude could make an incorrect change.
Below are a few screenshots showing the flow.
In this design, only Slack and GitHub are third-party software. For a while, I considered using Vercel, but since I already have my own server, it would be foolish to pay extra for just deployment.