Hubfly space for AI agents

Your agent can ship it.You stay in control.

Install one portable Markdown skill to teach your coding agent Hubfly space's current CLI workflow—from schema-v2 configuration and cloud reconciliation to Dashboard plans, deployment sessions, and verified operations.

Project workflow01 / 03
01
SourceOne portable Markdown file
02
ControlFull CLI coverage
03
ReleaseApproval before mutations
Hubfly space projectNetwork · volumes · domains · team access
One project model

Install

Add the skill to your project.

The portable project path is the simplest default. The same SKILL.md can also be placed in your agent's native skill directory.

terminal

$ mkdir -p .agents/skills/hubfly-cli
$ curl -fsSL https://hubfly.space/skills/hubfly-cli/SKILL.md \
-o .agents/skills/hubfly-cli/SKILL.md

Agent products may use different discovery directories. The file itself follows the portable Agent Skills format and does not contain credentials or executable scripts.

Portable project

.agents/skills/hubfly-cli/SKILL.md

Shared convention for compatible coding agents

Codex

.codex/skills/hubfly-cli/SKILL.md

Project-scoped Codex installation

Claude Code

.claude/skills/hubfly-cli/SKILL.md

Project-scoped Claude Code installation

Cursor

.cursor/skills/hubfly-cli/SKILL.md

Project-scoped Cursor installation

Prerequisite

Install and authenticate the CLI once.

The skill operates through the open-source Hubfly space CLI, which builds locally and uses the Dashboard control plane for plans, regional uploads, deployment sessions, reconciliation, and final status.

hubfly-cli

$ curl -fsSL https://raw.githubusercontent.com/hubfly-space/hubfly-cli/main/install.sh | bash
$ hubfly version
$ hubfly login
$ hubfly whoami

Workflow

Inspection first. Verified result last.

The skill gives agents enough deployment knowledge to be useful while keeping infrastructure changes under your control.

01

Inspect

The agent reads the app, schema-v2 manifest, ports, volumes, resources, and environment-variable names.

02

Reconcile

It compares explicitly managed local fields with the Dashboard's bound cloud container.

03

Plan

It reviews the server plan, revision guard, and destructive operations before proposing a rollout.

04

Approve

It names the exact target and command, then waits for your confirmation before changing state.

05

Follow

It tracks the asynchronous deployment session and reports the real terminal result or exact failed phase.

Try it

Ask in plain language.

The agent chooses between single-app plans and deploys, cloud-config pull, Dockerfiles, Compose stacks, deployment-session diagnosis, and runtime operations based on the repository and your goal.

“Inspect this repository and deploy it to Hubfly space.”

“Compare my schema-v2 manifest with the bound cloud container and show the deploy plan.”

“Pull the current cloud configuration without exposing secret values.”

“Deploy this Compose stack and verify every service.”

“Diagnose this build ID from its deployment status and events.”

“Follow the API container logs and summarize the error.”

Safety boundary

No silent infrastructure changes.

Source inspection, existing status, events, and logs can run immediately. Configuration writes, project binding, deployment actions, updates, remote access, and stack teardown require your explicit approval. Removing stack volumes receives an additional data-loss warning.

Secrets stay secret

The skill never asks an agent to commit tokens or print secret environment values.

--yes is not permission

The flag suppresses a CLI prompt only after you approve the exact proposed operation.

Sessions are authoritative

A local build or regional upload is not reported as success until Dashboard reaches a terminal deployment state.

Ready for your agent

Install the skill. Describe the outcome.

Hubfly space handles the deployment path while your agent inspects, explains, asks, executes, and verifies.