Docspacxio 0.x

Docs.
How pacxio works.

The workflow, the files a factory gets, the commands and tools behind them, and what runs where.

A1
Structures
Boxes, labels, pouches
B1
MCP server
Local + cloud tools
A2
Commands
All with --json
B2
Licence
MIT core
Get started

Overview

pacxio turns a box brief into the files a factory takes: dieline, CMYK print PDF, finish plates and a preflight report. It runs inside your coding agent: dielines and 3D on your machine, factory files on our server. You describe the box; the agent asks what it needs and stops for your approval at each step.

  • Command lineEvery step is a command with JSON output, so agents and scripts can drive it.
  • MCP serverLocal tools and cloud services, available to your agent through a local stdio MCP server.
  • SkillThe workflow and its rules: what to ask, when to stop for you.
  • WorkbenchA local page to see each stage, rotate the 3D, leave notes and approve.
Get started

Install

Paste one line into Claude Code or Codex and the agent installs the plugin. Or run it yourself in a terminal.

$ uv tool install pacxio && pacxio setup --yes

Full install guide →

Get started

Your first box

Open a project folder and describe what you're packing: product, size, board, the words that go on it. The agent opens the workbench and walks you through the steps.

> make a mailer box for my candle brand, 240 × 170 × 70 mm, kraft

Lost track? pacxio next <job> says where the job is, who it is waiting for and what runs next.

Workflow

The steps

Each step is saved in the job folder. Change something and the steps after it run again.

  1. Brief: copy, size and board in one listYou confirm
  2. Concepts: AI images that set the directionYou pick
  3. Back view and flat: every panel at the box's real proportionsYou confirm
  4. Design: vector artwork on the dieline, type set by the engineAgent
  5. Dieline approval: the same data as the print fileYou approve
  6. 3D: fold the dieline with the artwork on itView only
  7. Preflight: checks before exportEngine
  8. Export: the factory file packEngine
Concepts never print. They show the look. The final artwork is rebuilt from the confirmed flat as vectors, and every word is set by the engine and outlined.
Workflow

Approvals

Only you approve. The agent can prepare everything, but it cannot confirm on your behalf: it records an approval only after you say so, with your words. You can also approve in the workbench.

The dieline approval is the one gate before export. If the design changes after you approve, the agent renders it again and asks again.

Workflow

Structures

Most FEFCO and ECMA box styles, plus bottle labels and pouches, generated at your size and material. Know the code? Start from it. Don't? Describe how the box ships and sells, and pacxio suggests two or three with 3D previews.

$ pacxio structures suggest --use ecommerce --no-tape --L 240 --W 170 --H 70
$ pacxio job init jobs/candle --fefco 0427 --L 240 --W 170 --H 70
Maturity is stated per structure. Structures not yet checked against a real sample come with a note to order a proof first.
Output

Factory file pack

One folder to send to the factory, plus an archive you keep.

  • production.pdfPrint file in layers: artwork, cut, crease, each finish, glue area. Lines are named spot colours, overprinted.
  • spec.pdfSpec sheet: size, board, finishes, key colours and every check.
  • dieline.dxfCut and crease lines for the die maker, in mm.
  • ArchiveApproved dieline image, 1:1 proof, preflight report, CF2 dieline, separate finish plates.
Proof before mass production. The CF2 dieline has not yet been checked by a die maker.
Output

Preflight

Thirty-plus checks run before export: bleed, safe areas, fonts outlined, line colours, overprint, finish plates, total ink and more. Any error stops the export, and each comes with a fix. Warnings are passed on to you as they are.

$ pacxio preflight jobs/candle
$ pacxio export jobs/candle --proof --require-approval
Reference

Commands

The ones you'll see most. Run pacxio --help for all of them.

  • nextWhere the job is and what runs next
  • structuresSearch, show, suggest, preview, check, files
  • job initCreate a job and its dieline
  • studio startOpen the local workbench
  • conceptConcept prompts, import, choose a direction
  • art · finish · colorArtwork, foil and spot UV, key colours
  • renderDieline approval image
  • mockup3D views
  • preflight · exportChecks and the factory pack

Every command takes --json and returns {ok, command, job, artifacts, data, errors, warnings}. Exit codes: 0 done, 1 errors found, 2 bad arguments, 3 something missing on the machine.

Reference

MCP tools

The MCP server runs on your machine and communicates with your agent over stdio. It handles local tools and forwards layout, vector processing, preflight and export requests to the cloud.

  • StructuresSearch, suggest, show, preview, check, edit parameters, create a job
  • Jobjob_next, studio_open
  • Everything elsepacxio_run runs any command; pacxio_help lists them
  • Approvalsuser_confirm records what you said, word for word
$ pacxio mcp doctor
Reference

Workbench

A local page with every stage of the job: concepts, flats, the dieline approval, the 3D you can turn and fold. Click on an image to leave a note; the agent reads notes first on its next turn. It listens on 127.0.0.1 only and loads nothing from the internet.

$ pacxio studio start jobs/candle
About

Open source and cloud

Dielines and 3D are yours. The heavy lifting runs in the cloud.

On your machine MIT

  • Dieline engine: every structure in the library, at your sizes
  • 3D fold preview, with your own artwork
  • Import a DXF or PDF dieline and see it in 3D
  • Local workbench, Skill and MCP server with cloud access

In the cloud Free in early access

  • Layout and typesetting on the dieline
  • Concept flats turned into editable vectors
  • Full preflight, foil and spot-UV separations
  • The factory file pack