Skip to content

Add CLI generator overview page (pre-release) #5292

Open
fern-api[bot] wants to merge 4 commits intomainfrom
fern/cli-generator-page
Open

Add CLI generator overview page (pre-release) #5292
fern-api[bot] wants to merge 4 commits intomainfrom
fern/cli-generator-page

Conversation

@fern-api
Copy link
Copy Markdown
Contributor

@fern-api fern-api Bot commented May 1, 2026

Adds a high-level overview page for the CLI generator under the SDKs > Generators section, marked as pre-release.

The page focuses on use cases rather than implementation details or setup:

  • Why generate a CLI (automation, consistent DX, faster time-to-first-call, internal tooling)
  • What the generated CLI includes (mapped commands, auth, structured output, help text, completions)
  • Common use cases table
  • How the CLI generator complements SDKs

Requested by: Fern Support

@fern-api fern-api Bot requested a review from devalog as a code owner May 1, 2026 12:09
@fern-api
Copy link
Copy Markdown
Contributor Author

fern-api Bot commented May 1, 2026

Requested by: devin
Slack thread: View conversation

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 1, 2026

🌿 Preview your docs: https://fern-preview-fern-cli-generator-page.docs.buildwithfern.com/learn

Here are the markdown pages you've updated:

---

<Note title="In Development">
The CLI generator is currently in development. [Contact us](https://buildwithfern.com/contact) to learn more or request early access.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[FernStyles.Current] Avoid time-relative terms like 'currently' that become outdated


Fern's CLI generator produces a fully functional command-line tool from the same API spec you already use for SDKs. It ships as a single binary with no runtime dependencies — built for both AI agents that need deterministic, introspectable interfaces and human developers who want to script, debug, and explore.

## Why a CLI and why now
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[FernStyles.Current] Avoid time-relative terms like 'now' that become outdated


Human developers want CLIs too — for scripting, CI, debugging, and exploring an API before committing to an SDK integration. Both audiences are well-served by a single binary.

Most API companies don't ship one because building a good CLI is a multi-quarter project: commands, auth, pagination, retries, output formatting, cross-platform builds, shell completions, and keeping it all in sync as the API evolves. The CLI generator handles all of that automatically.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.Wordiness] Consider using 'all' instead of 'all of'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant