Fern

@AnthropicAI Claude, @OpenAI Codex, and @cursor_ai already build through the terminal, making the command line the default interface between APIs and agents. But most APIs still don't ship a CLI. The same API spec that powers Fern Docs and SDKs can now generate a fully functional CLI alongside them. Fern generates the CLI as a statically linked @rustlang binary that works as: • A native CLI for agents and developers • An MCP server for clients like @claudeai and @ChatGPTapp

Modern development is agent-native. The terminal is the lowest-friction surface for agents to operate in, so we built a CLI generator. We’re onboarding early access customers now at: link.buildwithfern.com/demo-cli

Try it out on your docs by adding `?shakespeare=true` to any docs site built with Fern, like NVIDIA's: docs.nvidia.com/heavyai?shakes… April Fools idea crafted by @kapilgowru, Devin Logan, and Sarah Bawabe. Read more: buildwithfern.com/learn/docs/cus…

Modern docs feel too casual. They lack the gravitas your product deserves. Today we've shipped Shakespeare mode for Fern Docs. Render thy docs in a noble verse! See it live: lnkd.in/gwdJdHqt Background music generated by @ElevenLabs

Documentation pages aren't static. As a feature matures, the job a page needs to do changes and the structure underneath needs to change with it. Fern's technical writer walks through three pages she recently rebuilt and what drove each one: link.buildwithfern.com/rebuilding-doc…

Now, docs reviewers don’t need a new preview link for every commit. Our new GitHub Action comments on your PR with: • A fixed, named preview link • Links to every changed page Learn more: link.buildwithfern.com/preview-action

Our only technical writer ships 20,000 new lines of docs a month. Here's how she actually uses AI (@AnthropicAI @cognition @NotionHQ) to do it — and what it still can't do on its own. link.buildwithfern.com/writer

Great docs should feel effortless. That means the small stuff matters—smooth arrows, no flickering icons, dialogs that ease open. Frontend engineer Sarah breaks down six small UI improvements she shipped to Fern Docs and why they're worth getting right: buildwithfern.com/post/ui-fixes

Here's what Elijah Skeirik, Technical Writer at Payabli, had to say about it: “Getting set up with the Rust SDK was genuinely a breath of fresh air. I ran like three commands, and then I could use our API with all of the thoughtful additions that Fern adds into their generated SDKs.”

𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗙𝗲𝗿𝗻'𝘀 𝗥𝘂𝘀𝘁 𝗦𝗗𝗞 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗼𝗿 🦀 Generate a type-safe Rust SDK from your API spec — with async/await, streaming, and idiomatic error handling. Built for performance-critical applications. Includes wire tests to verify correctness and one-command publishing to crates.io. Read more: buildwithfern.com/post/rust-sdk-… Built by Naman Anand

Overlays are an official OpenAPI standard that customizes a spec without modifying the original file. Add extensions, rename parameters, or use different configs for SDKs vs Docs — all while keeping your source spec clean. OpenAPI + Overlays = (𝘣𝘦𝘵𝘵𝘦𝘳) OpenAPI

𝗡𝗼𝘄 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗶𝗻𝗴 @OpenApiSpec 𝗼𝘃𝗲𝗿𝗹𝗮𝘆𝘀 Learn more: buildwithfern.com/learn/api-defi… Built by Thomas Baker

Making our docs even more AI-friendly

You can now assign roles to control what each team member can do in Fern: • Viewer – Read-only access in the dashboard. • Editor – Create and edit content in the Fern Editor. 𝘖𝘱𝘵𝘪𝘰𝘯𝘢𝘭: 𝘢𝘭𝘭𝘰𝘸 𝘊𝘓𝘐 𝘢𝘤𝘤𝘦𝘴𝘴 𝘧𝘰𝘳 𝘱𝘶𝘣𝘭𝘪𝘴𝘩𝘪𝘯𝘨 𝘚𝘋𝘒𝘴 𝘢𝘯𝘥 𝘋𝘰𝘤𝘴. • Admin – Full control of the organization, including publishing, member management, and billing. Built by Alec Harmon: linkedin.com/in/alecharmon/

𝗡𝗲𝘄: 𝗥𝗼𝗹𝗲-𝗯𝗮𝘀𝗲𝗱 𝗽𝗲𝗿𝗺𝗶𝘀𝘀𝗶𝗼𝗻𝘀 𝗶𝗻 𝗙𝗲𝗿𝗻 #permissions-by-role" target="_blank" rel="nofollow noopener">buildwithfern.com/learn/dashboar…

𝗡𝗲𝘄: 𝗔𝗜-𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗲𝗱 𝗲𝘅𝗮𝗺𝗽𝗹𝗲𝘀 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗔𝗣𝗜 𝗥𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 Fern generates realistic request and response examples for your API docs. Instead of generic placeholders, users now see believable examples that clarify how your API works. Read our docs: buildwithfern.com/learn/docs/ai-…