> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/updates-and-releases/cerby-cli/2026.md). # 2026 This article describes the newest features, enhancements, and bug fixes to improve your experience using the Cerby CLI. ## May 25, 2026 ### New features and enhancements * Running `cerby --help`, `cerby -h`, or `cerby` with no arguments now displays all available commands and global options. Previously, running `cerby` with no arguments exited with an error ### Fixes * The CLI login success page now shows "You are now logged in to the Cerby CLI" instead of the browser extension's success copy, and no longer triggers the extension's tab-close behavior. *** ## May 20, 2026 ### New features and enhancements * The `--workspace` flag is now available for the `login` command on macOS. With this flag, you can pass your workspace name directly to the command, skipping the workspace entry step in the web app during authentication. For example, `./cerby-macos login --workspace `. For more information, read the article [Authenticate with the Cerby CLI](https://help.cerby.com/developer-tools/cerby-cli/authenticate-with-the-cerby-cli). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.cerby.com/updates-and-releases/cerby-cli/2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.