---
title: CLI Walkthrough
url: "/learn/cli-walkthrough/"
canonical_url: https://docs.blossom88.com/learn/cli-walkthrough/
markdown_url: https://docs.blossom88.com/learn/cli-walkthrough.md
summary: Follow the CLI commands behind your first Blossom deployment and configure
  each resource yourself.
categories:
- cli
- learn
---

# CLI Walkthrough

Follow the commands your coding agent uses to plan, deploy, and update your
App. To run the setup yourself, [configure each resource](#configure-each-resource).

[Deploy with the CLI](/learn/getting-started/cli/) walks you through
your first deployment with one prompt.



<aside class="docs-callout not-typography" data-tone="info">
  
  <svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" aria-hidden="true"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z"></path></svg>
  
  <div class="docs-callout-body">
    
    <div class="info-content">
      
<p>You can preview your App before setting up billing. When you’re ready for your
first Blossom Cloud deployment, <a href="/docs/billing/">activate Cloud</a>
once for your Organization.</p>

    </div>
  </div>
</aside>



## Open your project

Open your project folder in a coding agent that can read files and run
terminal commands, such as Codex or Claude Code. Use the same project you've
been building so your agent has the code and context it needs.

Blossom builds your code from a Git repository: a copy of your project saved
on GitHub or another Git host. Your agent can help you publish your latest
changes and connect a private repository.

## Install and log in

Run these commands in your project's terminal, or ask your agent to run them.
Install on the machine where your agent runs:

    curl -fsSL https://cli.blossom88.com/install.sh | sh
    blossom login

Open the sign-in link yourself and choose your Account and a **Blossom Cloud**
Location, the region where your App will run. Your saved login remembers both.

Install the Blossom skill so your agent knows the deployment commands:

    blossom skill:install

To choose a specific agent, use `--agent codex` or `--agent claude`. Start a
fresh agent conversation in the same project after installation so it can
load the skill. See [Install and Log In](/learn/getting-started/install/)
for other setup options.

## With a coding agent


> **Ask your AI agent:** Deploy this project on Blossom. Show me the plan and wait for my approval.



Your agent checks the destination and prepares an **App Plan**, which
describes the application Blossom will run. For a project using the default
settings, the commands are:

    blossom profile:show
    blossom app_plan:create

The commands run from your project folder. For custom startup commands,
variables, or linked data, your agent can supply
[App Plan settings](/docs/reference/cli/app_plan/create/) with
`--data app_plan.yml`. It can also help you
[add a database](/learn/databases/) when your App needs one.

Review the plan with your agent:

| Check | What it means |
|---|---|
| Source | Your project and the version that will go live |
| Account and Location | Who owns the App and which region runs it |
| App and Environment | Your application's name and its live copy, usually called `production` |
| Services and data | The website, any background workers, and the database your App needs |

Ask for changes or approve in the conversation: **"Deploy it."** Your agent
uses the plan's ID to start the first deployment and follow its progress:

    blossom app_plan:deploy --id app_plan-100 --follow

`app_plan-100` is an example; your agent uses the ID Blossom returned. This
creates the App, its Environment, and Services together and starts deployment.

## Watch it go live

Your agent follows the build and deployment, then gives you the **App URL**
and a link to its **Environment** in Blossom. Open the App URL to use your
application. In the Environment, open **Activity** to see each deployment
step and its logs.

The terminal also prints the live URL beside `App:` when deployment finishes.
If a step needs attention, your agent can read its Activity and logs, explain
what happened, and propose a fix in the same conversation.

## Keep building

Make your next change with the agent, then ask:


> **Ask your AI agent:** Push my latest changes and deploy them to the same Environment.



After pushing the code, your agent deploys the same Environment:

    blossom environment:deploy --id environment-100 --follow

Your agent uses the Environment ID from the first deployment. App Plans
start new Environments; later updates use `environment:deploy`.

## Configure each resource

Create the App, set up its Environment, and deploy it with individual CLI
commands. The examples use a Sinatra App named `demo`.

1. [Install and log in](/learn/getting-started/install/).
2. [Choose your cloud and Location](/learn/getting-started/choose-your-cloud/).
3. [Create an App](/learn/getting-started/apps/).
4. [Set up the Environment](/learn/getting-started/environments/)
   with a Git repository, a web Service, and variables.
5. [Deploy and follow the logs](/learn/getting-started/deploy/).

If you're trying Blossom with a disposable project,
[clean it up when you're done](/learn/getting-started/cleanup/).

## What You Get

- Your own project running as a Blossom App
- A public HTTPS URL to open and share
- Deployment progress and logs in the terminal and browser
- The same coding agent ready to build and deploy your next change
