Skip to main content
The throughline of every recipe in this section is the same:
A local workflow produces something. The workspace holds it. The cloud uses it.
The “local workflow” could be a Bash script, a long-running Python job, a Claude Code session driving a browser, a Postgres dump, a model running on your GPU, or an ffmpeg pipeline. The “something” is a file — CSV, JSON, HTML report, image, model checkpoint, transcript, kanban board. Once it’s in the workspace, anyone (or any agent) can read it, edit it, query it over the REST API, or chat with it inside arg.ai.

​
The patterns

Sync a local folder

Mirror a local directory into the workspace, one-shot or continuously.

Agent loop with arg

Wire arg into Claude Code as MCP — the workspace is the agent’s memory.

Accumulate structured data

Each run appends a batch; the workspace file is the deduped source of truth.

Automations & reactions

.automation files: the workspace reacts when a file lands — 14 recipes.

Worked example

A real zero-server intelligence loop assembled from the patterns.

Developer templates

Apps to build on top of the workspace — dashboards, bots, portals.

​
About the arg CLI

The arg CLI is a small Go binary that wraps the REST API and stores your token in the OS keychain. Every recipe in this section assumes you’ve run arg login and arg workspace switch <name> once.
All commands accept --json for machine-readable output. arg upload and arg download handle multipart, resumes, and signed URLs.

​
Treat the workspace as a database: file formats that pay off

When the workspace is the durable side of these workflows, file choice matters. arg.ai ships first-class editors for several structured formats — use them instead of plain text so the data is queryable, editable, and visual without leaving the product.

​
When to use CLI vs MCP vs REST

The three speak to the same backend — pick whichever has the lowest friction for the surface you’re already in.
  • MCP guide — full tool list, scopes, and connection commands
  • Tools guide — REST equivalents the CLI and MCP both wrap
  • Servers guide — expose a long-running service from the workspace sandbox
  • API keys — credentials for headless scripts and CI