Metadata-Version: 2.4
Name: estampo
Version: 0.4.1
Summary: The build system for reproducible 3D prints. Define parts, slicer settings, and printer targets in code.
Project-URL: Homepage, https://estampo.dev
Project-URL: Repository, https://github.com/estampo/estampo
Project-URL: Issues, https://github.com/estampo/estampo/issues
Author-email: Paul Fremantle <paul@fremantle.org>
License:                                  Apache License
                                   Version 2.0, January 2004
                                http://www.apache.org/licenses/
        
           TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
        
           1. Definitions.
        
              "License" shall mean the terms and conditions for use, reproduction,
              and distribution as defined by Sections 1 through 9 of this document.
        
              "Licensor" shall mean the copyright owner or entity authorized by
              the copyright owner that is granting the License.
        
              "Legal Entity" shall mean the union of the acting entity and all
              other entities that control, are controlled by, or are under common
              control with that entity. For the purposes of this definition,
              "control" means (i) the power, direct or indirect, to cause the
              direction or management of such entity, whether by contract or
              otherwise, or (ii) ownership of fifty percent (50%) or more of the
              outstanding shares, or (iii) beneficial ownership of such entity.
        
              "You" (or "Your") shall mean an individual or Legal Entity
              exercising permissions granted by this License.
        
              "Source" form shall mean the preferred form for making modifications,
              including but not limited to software source code, documentation
              source, and configuration files.
        
              "Object" form shall mean any form resulting from mechanical
              transformation or translation of a Source form, including but
              not limited to compiled object code, generated documentation,
              and conversions to other media types.
        
              "Work" shall mean the work of authorship, whether in Source or
              Object form, made available under the License, as indicated by a
              copyright notice that is included in or attached to the work
              (an example is provided in the Appendix below).
        
              "Derivative Works" shall mean any work, whether in Source or Object
              form, that is based on (or derived from) the Work and for which the
              editorial revisions, annotations, elaborations, or other modifications
              represent, as a whole, an original work of authorship. For the purposes
              of this License, Derivative Works shall not include works that remain
              separable from, or merely link (or bind by name) to the interfaces of,
              the Work and Derivative Works thereof.
        
              "Contribution" shall mean any work of authorship, including
              the original version of the Work and any modifications or additions
              to that Work or Derivative Works thereof, that is intentionally
              submitted to Licensor for inclusion in the Work by the copyright owner
              or by an individual or Legal Entity authorized to submit on behalf of
              the copyright owner. For the purposes of this definition, "submitted"
              means any form of electronic, verbal, or written communication sent
              to the Licensor or its representatives, including but not limited to
              communication on electronic mailing lists, source code control systems,
              and issue tracking systems that are managed by, or on behalf of, the
              Licensor for the purpose of discussing and improving the Work, but
              excluding communication that is conspicuously marked or otherwise
              designated in writing by the copyright owner as "Not a Contribution."
        
              "Contributor" shall mean Licensor and any individual or Legal Entity
              on behalf of whom a Contribution has been received by Licensor and
              subsequently incorporated within the Work.
        
           2. Grant of Copyright License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              copyright license to reproduce, prepare Derivative Works of,
              publicly display, publicly perform, sublicense, and distribute the
              Work and such Derivative Works in Source or Object form.
        
           3. Grant of Patent License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              (except as stated in this section) patent license to make, have made,
              use, offer to sell, sell, import, and otherwise transfer the Work,
              where such license applies only to those patent claims licensable
              by such Contributor that are necessarily infringed by their
              Contribution(s) alone or by combination of their Contribution(s)
              with the Work to which such Contribution(s) was submitted. If You
              institute patent litigation against any entity (including a
              cross-claim or counterclaim in a lawsuit) alleging that the Work
              or a Contribution incorporated within the Work constitutes direct
              or contributory patent infringement, then any patent licenses
              granted to You under this License for that Work shall terminate
              as of the date such litigation is filed.
        
           4. Redistribution. You may reproduce and distribute copies of the
              Work or Derivative Works thereof in any medium, with or without
              modifications, and in Source or Object form, provided that You
              meet the following conditions:
        
              (a) You must give any other recipients of the Work or
                  Derivative Works a copy of this License; and
        
              (b) You must cause any modified files to carry prominent notices
                  stating that You changed the files; and
        
              (c) You must retain, in the Source form of any Derivative Works
                  that You distribute, all copyright, patent, trademark, and
                  attribution notices from the Source form of the Work,
                  excluding those notices that do not pertain to any part of
                  the Derivative Works; and
        
              (d) If the Work includes a "NOTICE" text file as part of its
                  distribution, then any Derivative Works that You distribute must
                  include a readable copy of the attribution notices contained
                  within such NOTICE file, excluding those notices that do not
                  pertain to any part of the Derivative Works, in at least one
                  of the following places: within a NOTICE text file distributed
                  as part of the Derivative Works; within the Source form or
                  documentation, if provided along with the Derivative Works; or,
                  within a display generated by the Derivative Works, if and
                  wherever such third-party notices normally appear. The contents
                  of the NOTICE file are for informational purposes only and
                  do not modify the License. You may add Your own attribution
                  notices within Derivative Works that You distribute, alongside
                  or as an addendum to the NOTICE text from the Work, provided
                  that such additional attribution notices cannot be construed
                  as modifying the License.
        
              You may add Your own copyright statement to Your modifications and
              may provide additional or different license terms and conditions
              for use, reproduction, or distribution of Your modifications, or
              for any such Derivative Works as a whole, provided Your use,
              reproduction, and distribution of the Work otherwise complies with
              the conditions stated in this License.
        
           5. Submission of Contributions. Unless You explicitly state otherwise,
              any Contribution intentionally submitted for inclusion in the Work
              by You to the Licensor shall be under the terms and conditions of
              this License, without any additional terms or conditions.
              Notwithstanding the above, nothing herein shall supersede or modify
              the terms of any separate license agreement you may have executed
              with Licensor regarding such Contributions.
        
           6. Trademarks. This License does not grant permission to use the trade
              names, trademarks, service marks, or product names of the Licensor,
              except as required for reasonable and customary use in describing the
              origin of the Work and reproducing the content of the NOTICE file.
        
           7. Disclaimer of Warranty. Unless required by applicable law or
              agreed to in writing, Licensor provides the Work (and each
              Contributor provides its Contributions) on an "AS IS" BASIS,
              WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
              implied, including, without limitation, any warranties or conditions
              of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
              PARTICULAR PURPOSE. You are solely responsible for determining the
              appropriateness of using or redistributing the Work and assume any
              risks associated with Your exercise of permissions under this License.
        
           8. Limitation of Liability. In no event and under no legal theory,
              whether in tort (including negligence), contract, or otherwise,
              unless required by applicable law (such as deliberate and grossly
              negligent acts) or agreed to in writing, shall any Contributor be
              liable to You for damages, including any direct, indirect, special,
              incidental, or consequential damages of any character arising as a
              result of this License or out of the use or inability to use the
              Work (including but not limited to damages for loss of goodwill,
              work stoppage, computer failure or malfunction, or any and all
              other commercial damages or losses), even if such Contributor
              has been advised of the possibility of such damages.
        
           9. Accepting Warranty or Additional Liability. While redistributing
              the Work or Derivative Works thereof, You may choose to offer,
              and charge a fee for, acceptance of support, warranty, indemnity,
              or other liability obligations and/or rights consistent with this
              License. However, in accepting such obligations, You may act only
              on Your own behalf and on Your sole responsibility, not on behalf
              of any other Contributor, and only if You agree to indemnify,
              defend, and hold each Contributor harmless for any liability
              incurred by, or claims asserted against, such Contributor by reason
              of your accepting any such warranty or additional liability.
        
           END OF TERMS AND CONDITIONS
        
           APPENDIX: How to apply the Apache License to your work.
        
              To apply the Apache License to your work, attach the following
              boilerplate notice, with the fields enclosed by brackets "[]"
              replaced with your own identifying information. (Don't include
              the brackets!)  The text should be enclosed in the appropriate
              comment syntax for the file format. We also recommend that a
              file or class name and description of purpose be included on the
              same "printed page" as the copyright notice for easier
              identification within third-party archives.
        
           Copyright 2025 Paul Fremantle
        
           Licensed under the Apache License, Version 2.0 (the "License");
           you may not use this file except in compliance with the License.
           You may obtain a copy of the License at
        
               http://www.apache.org/licenses/LICENSE-2.0
        
           Unless required by applicable law or agreed to in writing, software
           distributed under the License is distributed on an "AS IS" BASIS,
           WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
           See the License for the specific language governing permissions and
           limitations under the License.
License-File: LICENSE
Keywords: 3d-printing,3mf,bambu,estampo,gcode,orcaslicer,pipeline,slicer
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Manufacturing
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Topic :: Scientific/Engineering
Requires-Python: >=3.11
Requires-Dist: build123d>=0.10.0
Requires-Dist: defusedxml>=0.7.0
Requires-Dist: questionary>=2.1.0
Requires-Dist: rectpack>=0.2.0
Requires-Dist: requests>=2.28
Requires-Dist: sf-hamilton>=1.82.0
Requires-Dist: trimesh[easy]>=4.0.0
Requires-Dist: typer>=0.15.0
Requires-Dist: watchfiles>=1.0.0
Provides-Extra: dev
Requires-Dist: mypy>=1.10.0; extra == 'dev'
Requires-Dist: packaging>=23.0; extra == 'dev'
Requires-Dist: pytest-cov>=6.0.0; extra == 'dev'
Requires-Dist: pytest>=8.0.0; extra == 'dev'
Requires-Dist: ruff>=0.4.0; extra == 'dev'
Requires-Dist: towncrier>=24.7.0; extra == 'dev'
Description-Content-Type: text/markdown

<p align="center">
  <img src="https://raw.githubusercontent.com/estampo/estampo/main/docs/images/estampo-logo-color-256.png" alt="estampo logo" width="128">
</p>

# estampo

[![PyPI version](https://img.shields.io/pypi/v/estampo)](https://pypi.org/project/estampo/)
[![CI](https://github.com/estampo/estampo/actions/workflows/ci.yml/badge.svg)](https://github.com/estampo/estampo/actions/workflows/ci.yml)
[![Python 3.11+](https://img.shields.io/pypi/pyversions/estampo)](https://pypi.org/project/estampo/)
[![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
[![codecov](https://codecov.io/gh/estampo/estampo/branch/main/graph/badge.svg)](https://codecov.io/gh/estampo/estampo)

**The build system for reproducible 3D prints.**

You can version your Code CAD, STEP and STL files. You can't version your slicer setup easily — estampo fixes that.

Define parts, slicer settings, and the full pipeline in one TOML file, commit it, and run it anywhere. Same repo, same config → same G-code, locally or [in CI](#cicd-example).

estampo is a thin orchestration layer around slicer CLIs — it wraps OrcaSlicer or CuraEngine (Docker-pinned, CI-friendly, diffable) and doesn't replace them. See [the comparison table](#why-not-just-use-the-slicer-cli-directly) for what estampo adds over the raw CLIs.

**estampo is for you if** you use code-CAD (build123d, OpenSCAD, cadquery), want to slice from CI, diff slicer settings in git, or need identical G-code across machines.

**It's not for you if** you want a GUI slicer with preview, one-click printing, or a tool that manages a single local printer from the couch — use [OrcaSlicer](https://github.com/SoftFever/OrcaSlicer) or your vendor's app for that. estampo wraps those tools; it doesn't replace them.

> **Safety:** estampo generates G-code from your configuration but does not verify that settings are safe for your specific printer. Incorrect temperatures, speeds, or missing supports can damage your printer or create a fire hazard. Always review sliced output before sending to a printer. `estampo validate` checks config structure and setting names — it does not check print safety. **Use at your own risk.**

Works with STL, STEP, and 3MF files, and pairs naturally with code-CAD tools like
[build123d](https://github.com/gumyr/build123d), [OpenSCAD](https://openscad.org),
and [cadquery](https://github.com/cadquery/cadquery) — and with AI coding assistants, since the whole workflow is plain text.

**Requires [Docker](https://docs.docker.com/get-docker/) and Python 3.11+.** estampo runs the slicer (OrcaSlicer or CuraEngine) in a pinned Docker image so every machine produces identical G-code. A local slicer install works as a fallback but is not recommended.

**Which engine?** Use **OrcaSlicer for Bambu Lab printers** and **CuraEngine for everything else**. The bundled profiles reflect this: estampo ships 35 Orca machine profiles (all Bambu Lab — A1, P1P, P1S, X1, X1 Carbon, X1E) and 643 Cura machine profiles (Creality, Prusa, Voron, Ultimaker, Anycubic, Elegoo, etc.). Picking Orca for a non-BBL printer means no bundled machine profile — you'd have to supply your own.

```toml
# estampo.toml — a multi-part print with slicer overrides

[[parts]]
file = "enclosure_base.step"
orient = "flat"
filament = 1                    # AMS slot 1: PETG-CF

[[parts]]
file = "enclosure_lid.step"
orient = "upright"
filament = 1

[[parts]]
file = "button_cap.stl"
copies = 4
filament = 2                    # AMS slot 2: PLA

[slicer]
engine = "orca"
version = "2.3.1"               # pinned for reproducibility

[slicer.orca]
printer = "Bambu Lab P1S 0.4 nozzle"
process = "0.20mm Standard @BBL X1C"
filaments = ["Generic PETG-CF @base", "Generic PLA @base"]

[slicer.orca.overrides]
sparse_infill_density = "25%"
enable_support = 1
brim_type = "auto_brim"

[pipeline]
stages = ["load", "arrange", "plate", "slice", "gcode-info", "pack"]

[pack]
command = "bambox repack {sliced_3mf}"
output = "{sliced_3mf}"
```

```bash
estampo run        # arrange → slice → pack, one command
```

```
  Output → estampo_output/enclosure
✔ Loaded 3 parts
✔ Arranged 3 parts onto plate  (256×256mm)
✔ Plate exported → plate.3mf
✔ Preview exported → plate_preview.3mf
✔ Sliced with OrcaSlicer 2.3.1 in 48s
✔ Print time: 3h 42m, 24.6g filament
✔ Packed → plate_sliced.gcode.3mf
```

## What estampo does

![estampo demo](https://raw.githubusercontent.com/estampo/estampo/main/docs/recordings/demo.gif)

1. **Define** parts + settings in `estampo.toml`
2. **Arrange** — bin-packs models onto the build plate
3. **Slice** — using a pinned slicer version (via Docker) for identical G-code across machines
4. **Post-process** — run command stages (pack for Bambu via bambox, upload to Klipper via Moonraker, template resolution, etc.). Works with any printer that takes G-code; vendor specifics live in command stages, not in estampo.

Everything is declared in a single TOML file. Lock the slicer version, pin the
profiles, and the output is reproducible on any machine or in CI.

![estampo pipeline](https://raw.githubusercontent.com/estampo/estampo/main/docs/images/pipeline.svg)

### Why not just use the slicer CLI directly?

OrcaSlicer and CuraEngine both ship excellent CLIs, and estampo is built on
top of them — it shells out to one or the other for the actual slicing work.
The goal isn't to replace either tool; it's to give you a reproducible
pipeline around them (arrangement, profile pinning, CI, post-processing)
without asking you to assemble the full invocation by hand each time.

| What you need to do | OrcaSlicer CLI | CuraEngine CLI | estampo |
|---------------------|----------------|----------------|---------|
| Load printer/process profiles | `--load-settings` for each JSON in the chain | `-j printer.def.json` + `-d` search paths for inheritance | `printer = "..."` / `process = "..."` in TOML |
| Set material / quality overrides | Edit JSON or pass inline overrides | Chain of `-j` files or `-s KEY=VALUE` per setting | `[slicer.orca.overrides]` / `[slicer.cura.overrides]` |
| Arrange multiple parts | Not supported — prepare the plate yourself | Not supported — manual positioning | Automatic bin-packing |
| Multi-part filament / extruder mapping | Prebuilt 3MF with per-object slot metadata | `-g -e0 -l a.stl -g -e1 -l b.stl` per mesh group | `filament = 1` per part |
| Reproducible builds | Track slicer binary + profiles yourself | Track all definition JSONs yourself | `version = "..."` in TOML + pinned Docker image |
| Partial re-runs | Re-slice the whole thing | Re-slice the whole thing | `--until plate`, `--only slice` |
| Version control | Shell scripts + scattered JSON overrides | Shell scripts + `-s` lists + JSON definitions | Single TOML file — git-diffable, reviewable |
| Run in CI | Install OrcaSlicer manually (needs display on some builds) | Install CuraEngine + definitions manually | `uses: estampo/estampo/action@v0` |
| Post-process (e.g. pack for Bambu) | Separate manual step | Separate manual step | `[pack]` command stage with variable substitution |
| Headless slicing | GUI builds can require an X server | CLI-only already | Docker container pinned to a specific slicer version |

With the slicer CLI alone, your build config ends up spread across shell
scripts, `-s` flag lists, and JSON definition files — hard to diff, review,
or commit as a coherent unit. estampo replaces that orchestration layer
with a single declarative TOML file; the slicer itself does all the actual
work.

### Works with AI assistants

GUI-based slicers require point-and-click interaction that AI assistants cannot
drive. estampo's text-based config is different — an AI assistant can read your
TOML, understand your print setup, suggest overrides, create CI workflows, and
validate the result, all without leaving the conversation.

We provide a ready-to-paste [AI setup prompt](docs/ai-setup-prompt.md) that
gives any AI assistant (Claude, ChatGPT, Copilot) enough context to add estampo
to a project from scratch — it scans the repo for model files, asks you a few
questions, and generates the config. This isn't an AI feature bolted on — it's
an architectural property of using text instead of a GUI.

## Best fit

estampo is best suited to:

- Hardware teams keeping CAD and manufacturing inputs in Git
- Engineers who want deterministic slicing in CI
- Teams using AI coding assistants to manage their build and print workflows
- Makers who want a declarative print workflow instead of slicer click-ops

If you mostly want interactive print setup in a GUI, use OrcaSlicer or Cura directly.

## Status

- Declarative print config in `estampo.toml`
- Multi-part arrangement
- Docker-based slicing with pinned slicer versions (OrcaSlicer, CuraEngine)
- Slicing for any printer supported by OrcaSlicer or CuraEngine
- Profile pinning into your repository
- CI slicing and artifact generation
- Printing handled by external tools (e.g. [bambox](#sending-prints-to-a-printer) for Bambu Lab) wired in as command stages

> **Warning:** estampo is in active early development. We are moving fast and breaking things — config format, CLI flags, and Python APIs may change between minor versions without deprecation. Pin your version if stability matters to you.

## Quick start

**Prerequisites:** Python 3.11, 3.12, or 3.13 (3.14 is not yet supported) and [Docker](https://docs.docker.com/get-docker/).
Docker is central to estampo — it runs the slicer (OrcaSlicer or CuraEngine) in a container with a pinned
version so every machine produces identical G-code. A locally installed slicer can be used as a
fallback but is not recommended.

```bash
pip install estampo
# or, to install as an isolated CLI tool:
pipx install estampo
# or, with uv:
uv tool install estampo
```

Generate a config with the interactive wizard, or dump a commented template:

```bash
estampo init                       # interactive wizard — discovers profiles and CAD files, creates TOML
estampo init --template            # dump a commented template
```

Or create `estampo.toml` by hand (see [full config reference](https://github.com/estampo/estampo/blob/main/docs/config.md)):

```toml
[pipeline]
stages = ["load", "arrange", "plate", "slice", "pack"]

[plate]
size = [256, 256]       # build plate dimensions in mm
padding = 5.0

[slicer]
engine = "orca"
version = "2.3.1"       # pin OrcaSlicer version for reproducibility

[slicer.orca]
printer = "Bambu Lab P1S 0.4 nozzle"
process = "0.20mm Standard @BBL X1C"

[slicer.orca.overrides]  # simple way to define print settings without editing JSON
sparse_infill_density = "30%"       # stronger infill
wall_loops = 3                       # extra wall strength
enable_support = 1
brim_type = "auto_brim"             # help adhesion
curr_bed_type = "Textured PEI Plate"

[[parts]]               # define multiple parts using STEP, STL or 3MF inputs
file = "frame.step"
rotate = [180, 0, 0]    # flip so mounting plate faces down
filament = "Generic PETG-CF @base"

[[parts]]
file = "wheel.stl"
copies = 5
orient = "upright"
filament = "Generic PETG-CF @base"
```

`orient` picks a preset (`"flat"`, `"upright"`, `"side"`, `"upside-down"`) and `rotate = [rx, ry, rz]` takes degrees about X, Y, Z and overrides `orient`. See [Orientation](https://github.com/estampo/estampo/blob/main/docs/config.md#orientation) in the config reference for what each preset does and when to use which.

Run it (see [full CLI reference](https://github.com/estampo/estampo/blob/main/docs/cli.md)):

```bash
estampo run                   # run every stage in pipeline.stages
estampo run --until slice     # stop after slicing
```

The arrangement (`plate`) stage generates a `plate_preview.3mf` — open it in any 3MF viewer to check placement:

![plate preview](https://raw.githubusercontent.com/estampo/estampo/main/docs/images/plate_preview.png)

## Reproducibility

Pin profiles into your repo so builds are identical across machines:

```bash
estampo profiles pin          # copies slicer profiles into ./profiles/
git add profiles/              # commit to lock them
```

Combined with a pinned `version` in `[slicer]` (which locks the Docker image), the same config always produces the same gcode.

> **CuraEngine: pin non-bundled printers.** If your config uses a printer definition that isn't shipped with estampo (e.g. `bambox_p1s`), `estampo profiles pin` is **required**, not optional — the definition only exists inside the Docker image. Without it, `estampo run --local` fails and a teammate who clones the repo gets an empty `profiles/` directory. `estampo init` will remind you when you pick a non-bundled CuraEngine printer.

### CI/CD example

Automate slicing in GitHub Actions — push a commit, get G-code as a build artifact with print metrics on your PR:

```yaml
# .github/workflows/slice.yml
name: Slice
on: [push, pull_request]
jobs:
  slice:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: estampo/estampo/action@v0
```

The action slices your model, uploads G-code as an artifact, and posts print time / filament stats as a PR comment. See [`action/README.md`](action/README.md) for all options.

## CLI overview

```bash
estampo --version                   # print version
estampo init                        # interactive config wizard
estampo init --template             # dump commented TOML template
estampo init --workflow             # wizard + GitHub Actions workflow
estampo validate                    # check config for issues
estampo info                        # list valid stages, engines, orient values, substitution variables
estampo run                         # full pipeline
estampo run --until plate           # stop after plating
estampo run --only slice            # run just one stage
estampo profiles list               # list available slicer profiles
estampo profiles list --printer "Bambu Lab P1S 0.4 nozzle"   # processes/filaments compatible with a printer
estampo profiles pin                # pin profiles for reproducible builds
```

### Shell completion

estampo ships with Typer's built-in completion support:

```bash
estampo --install-completion        # install completion for your current shell (bash/zsh/fish/pwsh)
estampo --show-completion           # print the completion script without installing
```

After installing, restart your shell — you'll get tab completion for commands, flags, and stage names.

## Sending prints to a printer

estampo is **printer-agnostic**: it produces a sliced `.gcode.3mf` on disk and
stops there. Packing the output into a vendor-specific format and sending it
to a printer are handled by external CLIs wired into the pipeline as
[command stages](https://github.com/estampo/estampo/blob/main/docs/config.md#command-stages).
This keeps vendor-specific code out of estampo and lets you swap printer
backends without touching the build system.

### bambox (Bambu Lab)

For Bambu Lab printers, the companion CLI is
[bambox](https://github.com/estampo/bambox). estampo never imports bambox —
you install it separately and call it from your pipeline. Typical wiring:

```bash
pip install bambox
bambox login        # one-time — credentials saved to ~/.config/bambox/credentials.toml
```

For OrcaSlicer output, `bambox repack` regenerates the Bambu settings
in-place so the printer accepts the archive:

```toml
[pipeline]
stages = ["load", "arrange", "plate", "slice", "pack"]

[pack]
command = "bambox repack {sliced_3mf}"
output = "{sliced_3mf}"
```

For CuraEngine output, `bambox pack` wraps the raw `.gcode` into a
`.gcode.3mf`:

```toml
[pack]
command = "bambox pack {sliced_dir}/plate.gcode -o {output_dir}/plate.gcode.3mf"
output = "{output_dir}/plate.gcode.3mf"
```

To send the packed archive to a printer, add a stage that calls
`bambox print` — this uses Bambu Cloud and requires either the
`bambox-bridge` native binary (Linux x86_64) or Docker (macOS,
Windows, Linux ARM64). See the [AI setup prompt](docs/ai-setup-prompt.md)
for full examples including GitHub Actions wiring, and the
[bambox README](https://github.com/estampo/bambox) for bridge setup.

### Other printers

Any CLI that reads a sliced file and does something with it can be a
command stage. If your printer vendor has a CLI, wire it in the same way.
If it doesn't, `estampo run` already gives you a G-code file — hand it to
your printer however you normally would.

For Klipper-based printers with Moonraker, a one-line `curl` upload is
enough — no extra tool required:

```toml
[pipeline]
stages = ["load", "arrange", "plate", "slice", "send"]

[send]
command = "curl -F 'file=@{sliced_3mf}' -F 'print=true' http://moonraker.local/server/files/upload"
```

`{sliced_3mf}` is substituted by estampo with the path to the sliced
file. Set `print=false` if you want to upload without starting the job.

## Documentation

- [CLI reference](https://github.com/estampo/estampo/blob/main/docs/cli.md) — all commands, flags, and pipeline stages
- [Config reference](https://github.com/estampo/estampo/blob/main/docs/config.md) — complete TOML format
- [Developing](https://github.com/estampo/estampo/blob/main/docs/developing.md) — setup, testing, architecture

## Development

estampo's codebase is authored by [Claude](https://claude.ai), Anthropic's AI
assistant, under the direction and review of a human maintainer. Architecture
decisions, priorities, and acceptance criteria are set by the maintainer; Claude
writes the code, tests, documentation, and CI workflows. Every commit is
reviewed before merge.

## License

Apache 2.0
