Flowershow CLI
The fl CLI puts a folder of Markdown and HTML online as a site in one command and returns the URL and a claim link to an agent.
- 1,111 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- Publishing puts the folder's files on the open web, and a stray private note becomes reachable by link.
- The `fl delete` and `--overwrite` commands remove a live site with no way back.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/flowershow/flowershow/main/apps/cli/install.sh | shScript from the README for macOS and Linux. Set `FL_INSTALL_DIR` to skip `sudo`. Windows needs the archive from the releases.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Publishing puts the folder's files on the open web, and a stray private note becomes reachable by link.
- The `fl delete` and `--overwrite` commands remove a live site with no way back.
This is third-party code. Review the repository files before installing.
What it does
Flowershow is a platform for publishing notes, docs and wikis from Markdown and HTML. The `fl` console utility is written in Go and follows one flow: `fl ./my-notes` creates a site on the first run and syncs changes on every next one. For agents the utility has an accountless mode. `fl --anon --json ./folder` publishes a site without signing in and prints one JSON object with `url`, `claimUrl` and `expiresAt`, and the site lives 7 days until the owner claims it through the link. Sign-in usually goes through `fl login` in the browser, and CI can use a token in the `FLOWERSHOW_TOKEN` variable. The utility also lists and deletes sites, shows settings and handles annotations. A reader selects text on a page and leaves a note, and an agent pulls the notes with `fl annotations pull`, edits the files and closes the remarks.
Who it is for. Authors of Markdown and Obsidian notes and docs who need to put a folder online from a terminal or an agent chat.
Good fit when
- An agent finished a Markdown report draft, and the client needs to see it by link within the hour.
- A folder of Obsidian notes becomes a site with wiki links and no build setup.
- Publishing is wired into CI with a token in an environment variable.
- Readers leave remarks on a published page, and an agent works through them.
Not a fit when
- The content is not meant to be public: the site opens by link, and privacy is configured separately.
- You need a site on your own stack with a custom build: the utility publishes files to the Flowershow platform.
- The old Node package `flowershow` or `@flowershow/publish` is installed: it is deprecated and should be removed.
Example request
Publish the ./report folder as a site without an account through fl and give me the URL and the claim link.Limitations
The utility publishes to the Flowershow platform, and without signing in it creates a site that lives only 7 days. Installation on macOS and Linux runs a `curl ... | sh` script, so read `install.sh` first. Installing to `/usr/local/bin` may ask for `sudo`, and `FL_INSTALL_DIR` avoids it. Sites with an active premium subscription cannot be deleted until it is cancelled. Deleting and overwriting an existing site (`--overwrite`) cannot be undone. The utility collects anonymous usage statistics, which an environment variable switches off.
How to disable. Delete the `fl` binary from `/usr/local/bin` or from the `FL_INSTALL_DIR` directory, and run `fl logout` before removing it. Published sites are removed with `fl delete`.
FAQ
How do I install the Flowershow CLI?
On macOS and Linux run `curl -fsSL https://raw.githubusercontent.com/flowershow/flowershow/main/apps/cli/install.sh | sh`. On Windows download `fl_windows_amd64.zip` from the releases and add `fl.exe` to `PATH`.
How do I publish a site without signing up?
Run `fl --anon ./my-notes`. The utility prints the site address and a claim link. The site disappears after 7 days unless it is claimed into an account.
How can an agent read the publishing result?
Add the `--json` flag. All progress goes to stderr, and stdout gets one object with `ok`, `url`, `siteId`, `claimUrl` and `expiresAt`.
Which npm package should I use?
None. The `flowershow` and `@flowershow/publish` packages belong to the old Node client, and the README asks not to install them. Only the `fl` binary works.
What does the utility skip when publishing?
The `.git`, `node_modules`, `dist` and `build` directories, `.env` and `*.log` files, and everything listed in the published folder's `.gitignore`. The `.flowershow` service file also stays out of the site.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI and skill for an agent to publish reports and specs as HTML documents that a team comments on, with every version kept
Artifact Share CLI: an agent publishes HTML, Markdown and static sites at a stable link and updates it with new versions
A skill, an MCP server and a CLI turn Markdown from an agent into a short link to a web page that opens without signing in.
A plugin with a CLI and skills for Claude Code and Codex: agent-made HTML goes to a private AWS archive readable from a phone.
Diplodoc CLI (yfm-docs)
yfm-docs
Diplodoc platform CLI for building Yandex Flavored Markdown documentation with navigation and multiple languages
Pagecast CLI, skill and MCP server that publish HTML reports, Markdown and static sites to Cloudflare Pages behind a short link
README in short
The root README briefly shows installing `fl` and signing in, followed by a section for platform developers. The full command reference, the accountless mode and tips for agents live in the README of `apps/cli`.