You open up gmail and send an email to agent@recoupable.com

Generate an image for Wiz Khalifa's active campaign.

A new sandbox is created with Wiz Khalifa's file system. Claude Code is running your prompt. It looks at the docs to find the details of the active campaign, including the images you've already generated for the campaign. It looks at your mood board to understand reference images of Wiz Khalifa and the campaign. Claude generates an image and adds it to the campaign folder. It replies to your email attaching the photo it generated. It updates the progress file for the campaign noting the details of the created image. The sandbox is destroyed.

Why are sandboxes required? Couldn't record labels already do all of this with API endpoints and the Claude API? No, we couldn't. Simple APIs lack the following:

• File System

• Bash

Both are simple primitives which have existed since the first days of computing. APIs are great to trigger the creation of a sandbox. However, in serverless stacks like Cloudflare and Vercel, APIs lack both bash and the file system.

Bash is the command line. Bash is where Claude Code runs. Bash can read and write files, fetch web pages from urls, query APIs, open pull requests, basically anything you can do via a web page Claude Code can do via bash. However, bash is very powerful, it can run malicious commands which might corrupt your local file system or a shared system. By putting bash in a sandbox, we give Claude Code an isolated, untrusted, environment where it can execute tasks for your record label without corrupting your local computer. However, with Bash, we need a file system for files to be read from and written to.

File systems are where record labels get work done. It's what Claude Code directly reads / writes to with untrusted access. We give it a structure built for record labels with the following architecture:

• ORG.md - Rules for my record label.

• moodboard/ - Reference media for Claude Code to create media which references the record label's style.

• media/ - Media created by Claude Code for the record label.

• workspaces/[workspaceName]/ - All files for a musician, or other workspace within your record label. A grouping of files.

  • WORKSPACE.md - Rules for the musician.

  • moodboard/ - Reference media for Claude Code to create media which references the musician's style.

  • media/ - Media created by Claude Code for the musician.

Other than that, the file system is yours to customize. You can add anything from marketing templates to social media data tracking sheets. The more you use your Sandbox, the more customized it becomes, the better it understands your active campaigns which leads to higher quality outputs.

VPS is overkill. Sandbox provides just-in-time bash + filesystem.

Virtual Private Server (VPS) is a virtualized, isolated server partition within a physical machine, offering dedicated resources (CPU, RAM, storage) and root access for improved performance, security, and control over shared hosting. It acts as an independent server, allowing users to run custom operating systems and applications, commonly using Linux or Windows. 

You could absolutely spin up a VPS on Digital Ocean for $7 / month. It'll be your custom file system + bash. You could even run clawd.bot in it so you can directly talk to it via Telegram or phone call. But vps is expensive. If it's a record label with one employee, maybe that's fine. If you're a record label with 10+ employees, giving each a clawd.bot is now $70 / month. As clawd.bot runs, it fills more and more of your memory, especially if it's running non-stop, all the time. Now you need to worry about

• Pruning memory.

• Restarting the vps when (not if) there's an error that crashes your server.

• Dev ops for new server upgrades.

• etc.

Sandbox is just-in-time compute when and how you need it. Each prompt can specify a new

• Resources.

• Time alive.

• Runtime.

• File system image.

This makes the sandboxes for your record label flexible to help you keep costs low and iteration speed fast for any new changes you and your team need to make to daily label operations.

You open up gmail and send an email to agent@recoupable.com

Generate an image for Wiz Khalifa's active campaign.

A new sandbox is created with Wiz Khalifa's file system. Claude Code is running your prompt. It looks at the docs to find the details of the active campaign, including the images you've already generated for the campaign. It looks at your mood board to understand reference images of Wiz Khalifa and the campaign. Claude generates an image and adds it to the campaign folder. It replies to your email attaching the photo it generated. It updates the progress file for the campaign noting the details of the created image. The sandbox is destroyed.

Why are sandboxes required? Couldn't record labels already do all of this with API endpoints and the Claude API? No, we couldn't. Simple APIs lack the following:

• File System

• Bash

Both are simple primitives which have existed since the first days of computing. APIs are great to trigger the creation of a sandbox. However, in serverless stacks like Cloudflare and Vercel, APIs lack both bash and the file system.

Bash is the command line. Bash is where Claude Code runs. Bash can read and write files, fetch web pages from urls, query APIs, open pull requests, basically anything you can do via a web page Claude Code can do via bash. However, bash is very powerful, it can run malicious commands which might corrupt your local file system or a shared system. By putting bash in a sandbox, we give Claude Code an isolated, untrusted, environment where it can execute tasks for your record label without corrupting your local computer. However, with Bash, we need a file system for files to be read from and written to.

File systems are where record labels get work done. It's what Claude Code directly reads / writes to with untrusted access. We give it a structure built for record labels with the following architecture:

• ORG.md - Rules for my record label.

• moodboard/ - Reference media for Claude Code to create media which references the record label's style.

• media/ - Media created by Claude Code for the record label.

• workspaces/[workspaceName]/ - All files for a musician, or other workspace within your record label. A grouping of files.

  • WORKSPACE.md - Rules for the musician.

  • moodboard/ - Reference media for Claude Code to create media which references the musician's style.

  • media/ - Media created by Claude Code for the musician.

Other than that, the file system is yours to customize. You can add anything from marketing templates to social media data tracking sheets. The more you use your Sandbox, the more customized it becomes, the better it understands your active campaigns which leads to higher quality outputs.

VPS is overkill. Sandbox provides just-in-time bash + filesystem.

Virtual Private Server (VPS) is a virtualized, isolated server partition within a physical machine, offering dedicated resources (CPU, RAM, storage) and root access for improved performance, security, and control over shared hosting. It acts as an independent server, allowing users to run custom operating systems and applications, commonly using Linux or Windows. 

You could absolutely spin up a VPS on Digital Ocean for $7 / month. It'll be your custom file system + bash. You could even run clawd.bot in it so you can directly talk to it via Telegram or phone call. But vps is expensive. If it's a record label with one employee, maybe that's fine. If you're a record label with 10+ employees, giving each a clawd.bot is now $70 / month. As clawd.bot runs, it fills more and more of your memory, especially if it's running non-stop, all the time. Now you need to worry about

• Pruning memory.

• Restarting the vps when (not if) there's an error that crashes your server.

• Dev ops for new server upgrades.

• etc.

Sandbox is just-in-time compute when and how you need it. Each prompt can specify a new

• Resources.

• Time alive.

• Runtime.

• File system image.

This makes the sandboxes for your record label flexible to help you keep costs low and iteration speed fast for any new changes you and your team need to make to daily label operations.