Skip to main content

pacxio

Packaging, from a prompt.

Describe your packaging in Claude Code or Codex. Build editable dielines, turn and fold them in 3D, and review the design in a local workbench. Use the pacxio cloud service for artwork composition, preflight and factory delivery files.

Website · Install · Docs · Structure library · Online generator · Examples · PyPI

See it in action

A 51-second walkthrough: a brief in your coding agent, design choices, the dieline approval and the packaging workbench.

https://github.com/user-attachments/assets/a0312f38-b2d6-444b-a0ae-4d56e6c51edf

Watch on pacxio.dev

Made with pacxio

pacxio Dieline Tee

FEFCO 0427 mailer · 280 × 210 × 60 mm

A mailer for pacxio's own T-shirt: a blue-to-coral gradient, a silver-foil mark, and a design carried across the back and base. The concept sets the direction; the artwork is rebuilt on the dieline and previewed on the folded structure.

Concept Folded 3D preview
pacxio Dieline Tee concept pacxio Dieline Tee folded 3D preview
Open view Dieline proof
Open FEFCO 0427 mailer showing the inside and closure pacxio Dieline Tee artwork on its dieline

See the full gallery, including concepts, 3D views and dieline proofs →

Install

Paste this into Claude Code or Codex:

Read pacxio.dev/install to install pacxio

Or install from your terminal with uv:

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

For Codex, run pacxio setup --agent codex --yes instead. Setup installs the workflow Skill and MCP tools, and downloads the open-source Source Han Sans fonts if they are missing. Restart your agent after setup.

The plugin reads its full workflow and reference guides from the running MCP server, keeping the instructions and tools on the same version.

Then try a brief:

Make a T-shirt mailer, 280 × 210 × 60 mm.
Show me the dieline and folding 3D before we work on the artwork.

Full installation guide →

Updates

Automatic updates apply only to a standard, unpinned uv tool install pacxio from PyPI. pip, pinned versions, editable/source installs and custom-source installations remain manual. Eligible installations check in the background when MCP starts. A verified update is used on a later startup; your current session keeps its version. If a check or download fails, the working version remains available. Set PACXIO_AUTO_UPDATE=0 to turn automatic updates off.

Check the running and prepared versions locally with pacxio update status --json, or ask your agent to call pacxio_update_status. These diagnostics do not start an update.

The global pacxio command also uses the verified runtime. uv tool list shows the installed bootstrap package, which can differ from the version actually running. During a design session, your agent uses the connected MCP server's tools and guides together.

If you installed pacxio before this update mechanism, migrate once:

uv tool upgrade pacxio
pacxio setup --yes

Restart your agent afterward. Setup updates every supported agent found on your machine; add --agent codex or --agent claude-code to target one. To replace a running Workbench, run pacxio studio stop <job> and then pacxio studio start <job> --open. Your job files and saved choices stay in the job folder.

If MCP is unavailable, automatic updates through the plugin are unavailable too. You can still use the installed CLI manually with its matching workflow; the plugin's SKILL.local.md is a snapshot from installation.

Open-source core and cloud service

On your machine · this repository · MIT On the pacxio cloud service · sign-in required
FEFCO and public ECMA structures, plus carton, mailer, label and pouch entries Artwork composition and vector reconstruction
Editable geometry and dieline export: DXF, CF2 and PDF CMYK print PDF and named spot-color plates for foil, spot UV and embossing
Folding 3D preview and the local workbench Print preflight, specification sheet and factory delivery pack
Job records, content lists, concepts and review notes

The client routes cloud commands automatically. Run pacxio login to connect your account. Cloud commands send the required job files to the service and return previews, reports and delivery files to your local job folder.

How the open-source core and cloud service work → · Privacy

Command line

Preview a structure without creating a job:

pacxio structures preview 0427 --L 280 --W 210 --H 60 --out preview/

Or start a project and open its workbench:

pacxio job init jobs/demo --fefco 0427 --L 280 --W 210 --H 60 --material flute_e
pacxio studio start jobs/demo --open
pacxio next jobs/demo

Use pacxio structures suggest --use ecommerce --no-tape --material corrugated --json to find structures for a brief.

Commands accept --json and return {ok, command, job, artifacts, data, errors, warnings}. Errors include a suggested fix. Messages default to English; set PACXIO_LANG=zh for Chinese.

Browse the command guide →

Production checks

  • Print text is typeset by the engine and outlined. AI-generated print images must not contain text.
  • Concepts guide the design. Final artwork is rebuilt from confirmed flats before it goes on the dieline.
  • You approve the proof. Dieline approval is a user step; your agent must leave it to you.
  • Preflight errors block export. Fix them before generating factory files.
  • Dielines use lines and arcs. DXF R12 and CF2 do not contain Bézier curves.
  • Cut and crease lines use named spot colors and overprint. They are never drawn in Registration.
  • Check each structure's verification status. Values marked as initial need confirmation, and uncalibrated structures need a physical proof before production.

Development

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

Tests that need the closed-source package are skipped in an open-source-only installation. Fonts and ICC profiles are not bundled in this repository.

License and contact

The code in this repository is licensed under MIT. Cloud features are provided as a separate service.

Website · Documentation · Terms · support@pacxio.dev

Metadata

Release files for pacxio 0.0.4

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.4
File Size Uploaded Provenance Actions
pacxio-0.0.4.tar.gz 2.1 MB Without provenance Details for pacxio-0.0.4.tar.gz

Built distribution (wheel)

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

Total release size: 4.1 MB

Release files / pacxio-0.0.4.tar.gz

Download URL pacxio-0.0.4.tar.gz
Size 2.1 MB
Tags Source
SHA-256 checksum
How to use checksums
8964020d229283ceca3c2b287f4cad0fb18c7f41db1105b1f2ac0b189e812c1a
BLAKE2b-256 checksum
How to use checksums
2d4f21008c3e4959f5a6ac85252878d937eb470fdd3ea48f01d5ac3c8f382480
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.4-py3-none-any.whl

Download URL pacxio-0.0.4-py3-none-any.whl
Size 1.9 MB
Tags Python 3
SHA-256 checksum
How to use checksums
51bf0a8817b973e92d362d8fb4fb66b43f863d98d1cb10b81f83b174408b7435
BLAKE2b-256 checksum
How to use checksums
9c1160d818c20f48d668357afc52b869e3adc6bf57c3b64eb699ed6586e50118
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.4

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