Cosmic CLI

Key Features

• •The interactive shell provides a persistent terminal session where you can navigate your Cosmic workspace like a filesystem using ls, cd, and pwd commands. It eliminates the need to prefix every command with 'cosmic' and allows executing system commands with the '!' prefix. This speeds up daily operations and reduces cognitive load.
• •Engage in conversational AI sessions with full context awareness using four distinct modes: ask (read-only), content (modify content), build (generate apps), and repo (code changes). Provide additional context via flags for types and links. This enables natural language interaction with your project.
• •Navigate your workspace hierarchy using familiar filesystem commands like ls, cd, cd .., and pwd. Quickly move between projects, object types, and parent directories without memorizing complex API paths. This makes the CLI intuitive for any developer.
• •Manage GitHub repositories, branches, pull requests, environment variables, and custom domains entirely from the CLI. The clone command auto-configures .env files with Cosmic API keys. Create and merge PRs, deploy previews, and manage domains without leaving the terminal. Benefits streamlined DevOps workflows.
• •Choose from Claude (Anthropic), GPT (OpenAI), and Gemini (Google) models. Set a default model using 'cosmic config set defaultModel' or override per command with the --model flag. List available models with 'cosmic models'. This provides flexibility to use the best AI for each task.
• •Use the 'content' command to create content at scale. The Content Agent researches topics, matches your existing content style, and creates properly structured objects in your Cosmic bucket. This automates content creation and ensures consistency.
• •Describe an application in natural language using the 'build' command, and the CLI generates a complete, production-ready application connected to your Cosmic project. It creates a GitHub repository and prepares deployment. This reduces scaffolding time from hours to minutes.

Use Cases

• •A developer wants to launch a recipe blog quickly. They run 'cosmic build -p "A modern recipe blog with search and category filtering"' which generates the full app with GitHub repo, then 'cosmic content -p "Create 5 recipes with images"' to add content, and 'cosmic deploy start --watch' to deploy live on Vercel. Outcome: fully functional blog in minutes.
• •A content team needs weekly product roundups. They create a scheduled content agent using 'cosmic agents create --type content --name "Weekly Roundup" --prompt "Create a weekly summary of new products" --schedule --schedule-frequency weekly'. The agent automatically produces content every week, saving manual effort.
• •A developer wants to add dark mode and a favorites feature to an existing project. They run 'cosmic update my-repo -p "Add dark mode and a favorites feature" -b theme'. The Code Agent analyzes the code, creates a feature branch, and commits changes. They create a PR and merge, with auto-deployment. Outcome: new features added without manual code changes.
• •An engineering team needs to fix accessibility issues across their codebase. They create a repo agent with 'cosmic agents create --type repo --name "Bug Fixer" --prompt "Fix accessibility issues" --run'. The agent analyzes the code and opens a PR with fixes. The team reviews and merges. Outcome: improved accessibility with minimal effort.
• •A publisher wants a multi-step content pipeline. They use 'cosmic workflows create' to set up a workflow with writer, editor, and publisher agents. Each step is processed in sequence, with the ability to monitor progress and cancel runs. Outcome: automated content publishing pipeline.

Who is this for?

The Cosmic CLI is designed for developers who prefer terminal-based workflows, including full-stack developers, frontend engineers, and DevOps specialists. Content managers and strategists who want to automate content creation and publishing will also benefit. Technical founders building MVPs and product teams managing multiple projects can leverage the CLI for rapid prototyping and deployment. Additionally, platform engineers integrating AI agents into CI/CD pipelines and teams using AI workflows for multi-step automation will find the CLI essential. The tool supports individual developers and teams with role-based access control, making it suitable for small startups to larger organizations.