BY · TORCHSTELLAR

Every project.
One workspace.
One workflow.

Create workspaces and run development, builds, and tests. Manage projects, variables, and shared credentials in One Desktop, with shared conventions for people and AI.

Start building

$curl -fsSL https://1cli.dev/install.sh | bash

Start here

Three ways to start.

Create a workspace with one create, list available templates with one templates, or describe your goal to an agent that uses One CLI.

Option one

Run one create

Start with an empty workspace. Run one create and choose a directory, then add apps, services, or shared libraries with one add.

Create a workspace

$ one create

No flags to memorize first

Choose a target directory

Use one add later for more projects

Explore one create

Option two

Run one templates

List the apps, services, and shared library templates bundled with your CLI, then add projects with one add.

List available templates

$ one templates

List templates in the terminal

Compare their type and purpose

Add projects with one add

Browse template source

Option three

Hand it to AI

Give your goal and One CLI commands to an AI coding tool. In an existing workspace, have it read README files and one.manifest.toml first.

one-line agent prompt

Please use One CLI to create a media-stack workspace, add an Expo mobile app, and start it with one dev.

Describe what you want to build

AI uses One CLI to create workspaces or add templates

Use one run to prepare dependencies and execute tasks

View the AI skill

Common commands

From project setup to daily development.

Follow prompts to create workspaces and add projects, then use one run for daily tasks. Scripts and AI can use explicit arguments and JSON output.

one create one add one run one env One Desktop one help

ONE CREATE

Start a project
with one command.

Run one create to choose a target directory, or pass the directory explicitly. Then use one add to add projects to the empty workspace.

PROMPTED CREATERun one create by itself to choose the target directory.

ADD PROJECTSRun one templates to list templates, then add projects with one add.

AUTOMATIONCI and AI use --yes and -o json for predictable output and errors.

View the AI skill Read the template guideone-cli/create

$one create

>opens the create wizard

·asks for a target directory

·writes workspace directories, AGENTS.md, and mise task configuration

ONE ADD

Keep building
after the project exists.

one add adds a project to an existing One workspace. You can run one add directly to use the picker, or pass the template name and project name in scripts.

PROMPTED ADDRun one add to choose the template and project name.

AUTOMATIONCI and AI use one add nextjs-app --name web --yes.

SYNC DEFAULTSTemplates generate project code and register local development commands.

View the AI skillone-cli/add

$one add

>checks that cwd belongs to a One project

·opens template and project-name prompts

·writes the new directory and records it in the project list

ONE RUN

Different projects.
One way to run them.

one run lists workspace tasks and uses mise to run development, builds, and tests. Select a project with -p; One prepares tools and dependencies as needed.

DISCOVER TASKSRun one run to see available tasks and choose what to execute.

DAILY DEVELOPMENTone dev -p web starts a project; one build -p web builds it.

FOLLOW LOGSMulti-task runs offer a log tree with search, scrolling, and task selection.

View the AI skillone-cli/run

$one dev -p web

>resolve project tasks and dependencies

·prepare tools, dependencies, and bound project variables

·start the dev service and show its original logs

ONE ENV

Manage variables.
Inject them when needed.

Sign in to Infisical in your browser with one login, then manage project variables with one env. New workspaces can run before you connect variable storage.

BROWSER LOGINThe system keyring stores your session. Check its status with one whoami.

PROJECT VARIABLESSaving the first variable initializes the binding. Organize values by environment and project folder.

SHARED CREDENTIALSConfigure shared credentials in One Desktop and inject them explicitly with one exec --global.

View the AI skillone-cli/env

$one env set API_URL -p web

>sign in first with one login

·enter the value in a hidden terminal prompt

·fetch and inject variables from Infisical when the project runs

ONE DESKTOP

Manage projects
on your desktop.

Open One Desktop to browse workspaces, add projects, and manage variables and shared credentials.

PROJECTSInspect configuration, add projects from templates, and review Manifest changes before saving.

SHARED CREDENTIALSManage publishing and operations credentials centrally, and inject them into terminal tasks when needed.

ACCOUNTS AND VARIABLESSign in to Infisical in Settings and manage variables by environment and folder.

one-cli/desktop

↗One Desktop

>open the One Desktop app

·manage workspaces, projects, and shared credentials

·manage project variables by environment

ONE HELP

Help AI find
the right command.

Use one help --all for the complete command catalogue, then a subcommand's --help for its options. Agents can combine this with README files and one.manifest.toml to choose project operations.

FULL CATALOGUEList every command supported by the installed version.

OPTIONSCheck a subcommand's --help for arguments and usage.

JSON RESULTSUse -o json and handle failures through error.code.

View the AI skillone-cli/help

$one help --all

>find commands supported by this version

·check subcommand options

·choose operations using project guidance

AGENT-READY WORKSPACE

Let agents read facts before touching the project.

One CLI is not another chat surface. It organizes manifests, project configuration, and structured errors into one engineering contract so Codex, Claude Code, and Cursor can confirm project facts before choosing commands, editing code, or recovering from failures.

Command help explains usage

Agents use `one help --all` and subcommand `--help` to check the commands, options, and usage supported by the installed version before acting.

one help --all

Manifest records project facts

`one.manifest.toml` records workspace identity, project paths, toolchains, and the Infisical binding. Agents read those facts before choosing a subproject or command.

one.manifest.toml

Teams own project instructions

one create generates AGENTS.md in the current CLI language. Teams maintain it afterward; adding projects does not overwrite it.

AGENTS.md

Errors include next steps

Commands support JSON output, and errors include `code`, `context`, and `remediation[]`. Agents can choose a recovery action without parsing free text.

error.remediation[]

Clear errors and recovery hints

When a command fails, you do not have to guess.

When creating, adding, or running projects fails, One CLI preserves the cause and provides recovery hints for common errors. People and AI can use the same details to continue.

Create projects

Wrong folder or existing target: it tells you how to continue

Add projects

Template, name, or location issues come with a fix command

Run tasks

Missing config or tools are called out before you continue

Connect AI

The same result can be emitted as JSON for tools

>one add react-spa --name web --yes

No One CLI workspace found. Run this from a workspace root.
  - This folder is missing one.manifest.toml.
    Create a workspace first, or cd into an existing one:
    one create <dir>

Structured errors include a code and context. Scripts and AI can read the remediation field when recovery hints are available.

Bring your projects together. Get them running.

Start with an empty workspace, add projects as you need them, and use the same commands for daily development.

Start building GitHub

Every project.One workspace.One workflow.