Agent workflow

Deploy HTML from the CLI.

Install the HTMLHost.ai CLI once, then let Codex, Claude Code, Cursor, scripts, and CI tasks deploy generated HTML reports or previews without opening a browser.

Get API key Agent setup

$ npm install -g @htmlhost/cli
$ htmlhost login
$ htmlhost deploy report.html

# or without a global install
$ npx @htmlhost/cli deploy report.html

Deployed: https://yourname.htmlhost.ai/p/7m2/report.html

Shell-native HTML hosting

Any agent that can run terminal commands can publish the HTML file it just created.

Stable updates

Use htmlhost update when a review link should stay the same across iterations.

Account-owned pages

API keys tie published artifacts to an owner, which keeps abuse controls practical.

Copy-paste setup

Paste this into AGENTS.md or CLAUDE.md.

## Publishing HTML artifacts

When you create or update a standalone HTML artifact
(report, dashboard, prototype, test page):

1. Run: htmlhost deploy <file>.html
2. Reply with the public URL it prints.

To keep an existing URL stable across iterations, run:
htmlhost update <existing-url> <file>.html

Codex

Add a final instruction that Codex should deploy generated HTML artifacts and return the HTMLHost.ai URL.

Claude Code

Use the CLI from the same shell environment where Claude Code creates reports, prototypes, and dashboards.

Cursor and scripts

Any shell-capable editor, agent, script, or CI task can publish a standalone HTML file with the same command.

FAQ

Practical answers before you publish.

Is the CLI published on npm?

Yes. Install it globally with npm install -g @htmlhost/cli.

Can I use npx instead?

Yes. npx @htmlhost/cli deploy report.html works when you do not want a global install.

Where does login store credentials?

The CLI stores the API key in the user config directory with user-only file permissions.

Can the CLI update the same URL?

Yes. Use htmlhost update with an existing HTMLHost.ai URL and a replacement HTML file.