Skip to main content

pacxio

Packaging prepress for coding agents. Describe a box, and pacxio turns box dimensions and brand artwork into the files a packaging factory accepts:

  • the dieline: DXF, CF2 and PDF;
  • a CMYK print PDF;
  • named spot-color plates for foil, spot UV and embossing;
  • a spec sheet;
  • a preflight report.

pacxio runs inside Claude Code or Codex as a plugin (a workflow Skill plus MCP tools), and as a plain command-line tool.

What runs where

On your machine (this repository, MIT) On the pacxio server (sign-in required)
Structure library: FEFCO and public ECMA codes, plus hand-built carton, mailer, label and pouch entries Composing artwork onto the dieline (render, art, restore, visual trace)
Dieline geometry, editable parameters, DXF / CF2 / dieline PDF Print PDF, spot-color separations, preflight
Folding 3D preview and the local workbench (127.0.0.1 only) The factory delivery pack (export)
Jobs, content lists, concept-image records, notes

The open client sends server-side commands to the pacxio server automatically. Every command prints the same JSON either way. The first such command starts a browser sign-in (pacxio login). Your vector artwork stays on the server; previews, reports and the delivery pack come back to your job folder.

Install

You need uv.

uv tool install pacxio
pacxio setup --agent claude-code --yes

Use --agent codex for Codex. Leave out --agent to install into every agent found on the machine. Setup also downloads the open-source Source Han Sans fonts if they are missing. Restart the agent afterwards, open a project folder, and describe the box you want.

Command line

pacxio structures suggest --use ecommerce --no-tape --material corrugated --json
pacxio structures preview 0427 --L 233 --W 161 --H 66.5 --out preview/
pacxio job init jobs/demo --fefco 0427 --L 233 --W 161 --H 66.5 --material flute_e
pacxio studio start jobs/demo --open
pacxio next jobs/demo
  • structures suggest picks candidate structures from the library for what the box has to do.
  • structures preview draws a dieline and a 3D view without making a job.
  • studio start opens the local workbench in your browser.
  • next tells you which step comes next and which command runs it.

Every command takes --json and prints {ok, command, job, artifacts, data, errors, warnings}. Each error carries a fix. Exit codes: 0 success, 1 an error was found, 2 bad arguments, 3 something is missing from the environment.

Messages are in English. Set PACXIO_LANG=zh for Chinese.

Rules the engine enforces

  • Text in print files is typeset by the engine and outlined. AI-generated images in print files must not contain text.
  • Concept images are for direction only. The engine refuses to place a concept image in a print file. The final artwork is rebuilt from the confirmed flat.
  • The user confirms; the agent does not. approve on the dieline confirmation image is the only gate before export.
  • A preflight error means no factory files. export refuses until every error is fixed.
  • Dielines use lines and arcs only. No Béziers, so DXF R12 and CF2 stay exact.
  • Cut and crease lines are named spot colors set to overprint. They are never drawn in Registration.
  • Values marked as initial are not verified. Structures that are not calibrated against a factory dieline say so. Make a physical proof before a production run.

Development

uv sync
uv run pytest
uv run ruff check . && uv run mypy
uv run pacxio env check

Separation tests are skipped when Ghostscript is not installed. Fonts and ICC profiles are not part of this repository.

License

MIT. See LICENSE.

Metadata

Release files for pacxio 0.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pacxio 0.0.2
File Size Uploaded Provenance Actions
pacxio-0.0.2.tar.gz 1.4 MB Without provenance Details for pacxio-0.0.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pacxio 0.0.2
File Interpreter ABI Platform Actions
pacxio-0.0.2-py3-none-any.whl Python 3 none any Details for pacxio-0.0.2-py3-none-any.whl

Total release size: 2.6 MB

Release files / pacxio-0.0.2.tar.gz

Download URL pacxio-0.0.2.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
2183edbaa3ef6372109c4e4d7be769edd6344d3e4de9cb18923a47225f455f54
BLAKE2b-256 checksum
How to use checksums
9ae94f0fc014618e1abee11fe1ef0d2a95cc88204c19ab7aea04a21230770b46
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / pacxio-0.0.2-py3-none-any.whl

Download URL pacxio-0.0.2-py3-none-any.whl
Size 1.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
e0ca6630ab28b3d7731ac12ba0882a917cc27a1854f6416a908afeca3f16fcd1
BLAKE2b-256 checksum
How to use checksums
3d64e3c9e8c81f10bb99f350b02f78a245d33d14499fe51fb7ef574814c74cd6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for pacxio 0.0.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page