Command-line client
aland
— publish artifacts from your terminal
aland is the command-line client for
artifact.land.
It publishes HTML and JSX artifacts straight from your working directory — and it gives coding agents
(Claude Code, Cursor, your own scripts) a safe way to publish on your behalf. Every programmatic
publish lands as a draft; going live is always a click from you.
Install
Homebrew — macOS + Linux
brew install artifactland/tap/aland
Quickstart
Fork someone else's artifact into your own copy, edit it, preview it, publish.
aland login aland fork @alice/mortgage-calculator # edit the code aland preview aland push
aland push creates a draft
in your account and prints the URL. Open it, check the preview, hit Publish when it's
ready to go live.
Starter prompts
Paste one of these into Claude, Cursor, or your coding agent of choice.
The first line tells the agent aland
exists; aland context is a
self-contained briefing that teaches it the runtime, sandbox, and workflow in one shell call.
Run aland login once first so
your agent can push drafts under your account.
Build something new
Hey Claude, I have a CLI called `aland` installed. Run `aland context` to learn how it works, then help me build an interactive artifact about [YOUR IDEA HERE]. When it's ready, push it as a draft so I can review in the browser before publishing.
Fork and remix
Hey Claude, I have a CLI called `aland` installed. Run `aland context`, then fork https://artifact.land/@alice/mortgage-calculator and change [WHAT YOU WANT CHANGED]. Push the result as a draft.
Fix a bug in your own
Hey Claude, I have a CLI called `aland` installed. Run `aland context`, then pull https://artifact.land/@me/my-artifact. There's a bug where [DESCRIBE IT]. Fix it and push — I'll review the draft and publish if it looks good.
Why a CLI
Coding agents generate a lot of interactive code — prototypes, one-off tools, explanations, visualizations. Most of it never leaves the sandbox it was generated in. We wanted a bridge: one command that hands a finished artifact to your account, so you can look at it in a browser and decide whether it's ready to share.
The CLI is that bridge. It's built for the workflow where an artifact is a file on disk — whether you wrote it, Claude wrote it, or an agent running on your behalf did. Every programmatic publish lands as a draft; the "go live" step is always a deliberate click. You stay in control of what goes out under your name.
What's next
- Read the guide for the end-to-end publishing workflow.
- Follow @artifactland for updates and new features.
- Report issues on GitHub.