Skip to content

Let your agent upload files to Elaichi

Some tools need a file: attach a document to a task, post a spreadsheet to a channel. When the file is on your machine, or attached in your chat, your AI agent can send it to Elaichi by itself. You do not have to open a page or pick the file yourself.

Elaichi tries the options in this order, and asks you only as the last one:

  1. A file a tool already returned, or one the agent downloads from the app it lives in.
  2. Text or data the agent wrote. The agent saves it as a file in Elaichi.
  3. A file on your machine or attached in chat. The agent uploads it automatically:
    • An agent that can run commands (Claude Code, Cursor, Codex and similar) uploads it with one curl command.
    • ChatGPT sends the files you attached to Elaichi directly.
  4. Only if none of those works, the agent asks you to upload the file on a page in Elaichi. You choose the file and press Send.

You can see everything that arrives in Files. A file uploaded by your agent reads "Uploaded by ‹app›"; a file from ChatGPT reads "From ChatGPT". It is yours and private to you until you share it, and it is deleted after 7 days.

What the agent's upload can and cannot do

Topic What happens
One file, once The agent states the file's name, size and fingerprint first. The upload address works for that file only, once, for 10 minutes. If the bytes are not that file, Elaichi throws them away and the agent has to start again.
Who it belongs to The file belongs to you, the person who connected the agent. The upload address carries no sign-in and cannot read, list or replace anything.
Size Up to 95 MiB per file.
Audit log Each upload address and each finished upload is an entry in your audit log, with the name of the app that asked.
Limits At most 20 unused upload addresses at a time and 100 an hour per person.

Allow api.elaichi.ai where your agent runs

The agent uploads from the machine, sandbox or cloud environment where your file is. That place must be allowed to reach api.elaichi.ai over HTTPS. Many agents block outgoing network access by default. If yours does, the agent says the upload could not connect and falls back to the upload page. To keep uploads automatic, allow that one address.

The setting names below are the ones these tools use at the time of writing. If a menu or key has moved, look for the equivalent "allowed domains" or "network access" setting in your tool's documentation.

Claude Code

On your own machine, Claude Code's sandbox lists the addresses commands may reach. Add Elaichi to sandbox.network.allowedDomains in .claude/settings.json (this project) or ~/.claude/settings.json (all projects):

{
  "sandbox": {
    "enabled": true,
    "network": {
      "allowedDomains": ["api.elaichi.ai"]
    }
  }
}

In Claude Code on the web and other cloud environments, open the environment's settings and set network access to a custom list. Add api.elaichi.ai to the allowed domains.

Claude (claude.ai) code execution

When Claude runs code in a chat, outgoing network access is limited. In Settings, under Capabilities, find Code execution and file creation. Which choices you have depends on your plan, and we have not verified this against every plan:

  • Team and Enterprise: an organization owner sets the network access for everyone, and can add api.elaichi.ai to the list of allowed domains.
  • Free, Pro and Max: the setting may offer only a fixed choice, such as no network access, package managers only, or all domains, with no per-domain list. If you cannot add a domain, choose all domains for the chats where you want automatic uploads, or let the agent fall back to the upload page.

Cursor

Cursor's agent sandbox reads .cursor/sandbox.json (project) or ~/.cursor/sandbox.json (all projects). Allow Elaichi in its network policy:

{
  "networkPolicy": {
    "default": "deny",
    "allow": ["api.elaichi.ai"]
  }
}

Codex

Codex's local sandbox blocks network access by default. Turning it on in ~/.codex/config.toml allows every address, not just Elaichi:

sandbox_mode = "workspace-write"
 
[sandbox_workspace_write]
network_access = true

To allow only Elaichi, Codex now has per-domain rules through its network proxy (features.network_proxy.domains; the proxy is off by default). Turn the proxy on and add api.elaichi.ai to its domain list. The exact keys are in Codex's own documentation and may differ by version.

For Codex cloud environments, set the environment's internet access to a custom list and add api.elaichi.ai.

ChatGPT

Nothing to allow. ChatGPT hands the files you attached to Elaichi itself. Attach the file in the same chat where you ask for the task.

If the upload cannot connect

The agent says what happened and asks you to upload the file on a page in Elaichi instead. That page is always available. It only needs you signed in as yourself. You choose the file and press Send, which is your approval to hand it to the agent.