UiPath Documentation
uipath-cli
latest
false
UiPath CLI user guide

uip solution init

Syntax and options for `uip solution init`, which scaffolds an empty UiPath solution directory with a `.uipx` manifest.

uip solution init scaffolds an empty UiPath solution on disk. It creates a directory named after the solution, writes a .uipx manifest with an empty Projects array, and writes AGENTS.md and CLAUDE.md briefing files that orient AI coding agents to the solution — ready to receive projects via uip solution projects add or uip solution projects import.

Synopsis

uip solution init <solutionName>
uip solution init <solutionName>

The command honours the global options and returns the standard exit codes.

Arguments

  • <solutionName> (required) — Name or path for the new solution. A directory is created at this location; the .uipx file inside it takes the same base name.

Options

None beyond the global options.

Examples

Minimal

uip solution init my-solution
uip solution init my-solution

Creates ./my-solution/my-solution.uipx, plus ./my-solution/AGENTS.md and ./my-solution/CLAUDE.md.

Scripting — capture the generated path

uip solution init my-solution --output-filter "Data.Path"
uip solution init my-solution --output-filter "Data.Path"

Combined with --output json, emits a single JSON string with the absolute path to the new .uipx, suitable for piping into follow-up commands.

Data shape (--output json)

{
  "Code": "SolutionInit",
  "Data": {
    "Status": "Created successfully",
    "Path": "/workspace/my-solution/my-solution.uipx",
    "NextSteps": "Read /workspace/my-solution/AGENTS.md or /workspace/my-solution/CLAUDE.md to understand the solution lifecycle, project types that can be used inside a solution, and related uip command references."
  }
}
{
  "Code": "SolutionInit",
  "Data": {
    "Status": "Created successfully",
    "Path": "/workspace/my-solution/my-solution.uipx",
    "NextSteps": "Read /workspace/my-solution/AGENTS.md or /workspace/my-solution/CLAUDE.md to understand the solution lifecycle, project types that can be used inside a solution, and related uip command references."
  }
}

NextSteps points at whichever briefing file the invoking agent (or a human) should read next — it's the same content in both files, written for different coding-agent conventions.

See also

  • Synopsis
  • Arguments
  • Options
  • Examples
  • Minimal
  • Scripting — capture the generated path
  • Data shape (--output json)
  • Related commands
  • See also

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated