Skip to content
ErawanACADEMYไทย

Getting started

Claude Cowork — putting a page on Erawan

Cowork can build a page and put it on Erawan from the chat, and Claude does almost all of it. The one thing you may have to do yourself is let its sandbox reach Erawan. This lesson covers what to type, how the files get up, and where to click when you see a 403.

Want a hand from the start? Erawan gets your first app online for free on Hobby and above.

Haven't connected Claude to Erawan yet? Start with this lesson.

1. Ask Cowork to put it online

Say what you want and ask for it to go on Erawan. Claude picks how to send the files.

Build a landing page for a coffee shop with pictures of the menu, and put it on Erawan as coffee-demo

If the files already exist and you want them uploaded, just say so.

Put the files in this folder on Erawan with create_upload, not deploy_files

Most of the time Claude finishes on its own and hands you a link. If you see a 403, skip to step 3. That one you have to switch on yourself.

2. How the files get there

The files Cowork makes live in a sandbox, a temporary Linux machine where Claude makes files and runs commands. Your Erawan account lives in the connector you added when you clicked Connect. The two are kept apart on purpose: the sandbox runs whatever code it is given, and a key to your account sitting inside it could leak.

For a small page that is all text, Claude types the whole thing and sends it through the connector with deploy_files, which takes up to 512KB in total. For a bigger page, or one with pictures, Claude uses create_upload: it asks for an upload address through the connector, and the sandbox sends the files to that address.

The address works once, within 10 minutes, and only for sending files. If it leaked, nobody could put anything online with it, because that step still goes through your signed-in connector.

3. A 403 is yours to switch on

If you see 403 or CONNECT tunnel failed, the sandbox is not yet allowed to reach api.erawan.cloud. That answer comes from Claude's side, not Erawan's, and Claude cannot switch it on itself. Here is how you do it.

  1. Open claude.ai/settings/capabilities
  2. Under Code execution and file creation, turn on Allow network egress
  3. Under Domain allowlist, add api.erawan.cloud to Additional allowed domains. On a Team or Enterprise account, an owner sets this for the whole organization.
  4. Start a new chat so the setting is sure to apply

If you still see a 403 with everything set, it may be an open bug on Anthropic's side (#93562) where some sessions ignore the setting. Until it is fixed, Claude Code deploys as usual.

Other messages you might see

Claude usually fixes these itself. If one is stuck, tell Claude this.

  • 401 Missing bearer token Claude sent the files the way that needs an account. Tell it to use create_upload.
  • 401 This upload address has expired More than 10 minutes passed. Have Claude ask for a new address.
  • 409 This upload address has already taken an archive That address has already taken one set of files. If Claude did not send it, do not deploy it. Ask for a new address.
  • the limit is 512KB Too big to type out. Use create_upload.

All Erawan Cloud lessons