Skip to main content

adobepy

Shared Adobe desktop communication runtime for Python tools and DCC MCP adapters. Python talks to a local Rust broker; Adobe applications run thin UXP or CEP/ExtendScript bridges.

adobepy is intended to be the common Adobe host layer for projects such as dcc-mcp-photoshop and future Adobe adapters. The public Python surface mirrors Adobe's JavaScript DOM where possible, while adding Pythonic aliases for agent and script ergonomics.

Implemented pieces:

  • Rust adobepy CLI with broker, doctor, install-bridge, and repl.
  • python -m adobe helpers (doctor, install-bridge, broker) so a wheel-only install can be diagnosed and can stage a bridge from Python.
  • Local JSON-RPC broker with per-session token, target, timeout, and capability gates.
  • Authenticated, typed broker/host/bridge runtime identity attestation for exact-instance checks by DCC MCP adapters.
  • Bounded Photoshop UXP bootstrap with one-time exact-instance binding and a typed verification continuation; no arbitrary plug-in, command, script, or UI fallback.
  • Bounded Illustrator CEP bootstrap that binds the receipted bridge and selected product process to a one-time claim and fixed adapter verification command.
  • Python SDK under adobe.core, adobe.raw, adobe.photoshop, adobe.indesign, adobe.premiere, adobe.after_effects, and adobe.illustrator.
  • Structured, non-eval access to the complete installed InDesign, Premiere, After Effects, and Illustrator object models.
  • Optional DCC MCP result helpers under adobe.dcc_mcp for adapter skill code.
  • UXP bridge templates for Photoshop, InDesign, and Premiere that dispatch to host APIs and broker raw JavaScript escape hatches.
  • CEP bridge templates for After Effects and Illustrator.
  • IR validation, proxy-aware .pyi stub generation, and stub/runtime drift checks.
  • vx just package distribution workflow.

Validate everything:

npm install
npm run test:all

Bridge bundles under bridges/**/dist are generated artifacts and are not tracked. npm run test:all builds them for local verification; release CI rebuilds them before packaging. Run npm run uxp:build and npm run cep:build before using install-bridge directly from a source checkout.

The distribution name is adobepy and the import name is adobe. The PyPI wheel carries the SDK and the python -m adobe entry point; the broker executable and bridge templates ship in the platform bundle on GitHub Releases. Run python -m adobe doctor to see which parts are present and where to obtain the missing ones.

Installation, standalone use, broker startup, bridge loading, and troubleshooting are documented in install.md.

The full test suite type-checks bridge code, builds and exercises UXP/CEP bundles with mocked host runtimes, validates IR contracts, checks Python coverage, and runs Rust workspace tests.

Python support starts at 3.8. The current SDK wheel is pure Python; any future native Python extension must publish cp38-abi3-* wheels rather than per-minor-version wheels.

Build a redistributable Windows package:

vx just package

The archive is written to dist/adobepy-0.1.0-windows-x64.zip with a sibling SHA256 file. Usage and packaging notes are in docs/usage.md and docs/distribution-contract.md. Architecture boundaries and Adobe API source tracking are documented in docs/architecture.md, docs/api-sources.md, and docs/dcc-mcp-integration.md.

Python facade example:

from adobe.photoshop import Photoshop

app = Photoshop()
for layer in app.activeLayers:
    print(layer.name)

doc = app.activeDocument
doc.selection.select_rectangle({"top": 10, "left": 10, "bottom": 256, "right": 256})
for channel in doc.channels:
    print(channel.name)

text = app.activeText
if text:
    text.set_contents("Hello from Python")
    text.character_style.update(size=36, tracking=20)
    text.paragraph_style.update(justification="center")

layer = app.activeLayer
if layer:
    layer.filters.apply_gaussian_blur(2)
    layer.smart_object.convert_to_smart_object()

doc.exports.jpg_high("C:/renders/demo.jpg")

Metadata

Release files for adobepy 0.11.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 adobepy 0.11.2
File Size Uploaded Provenance Actions
adobepy-0.11.2.tar.gz 80.2 kB With provenance Details for adobepy-0.11.2.tar.gz

Built distribution (wheel)

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

Total release size: 169.9 kB

Release files / adobepy-0.11.2.tar.gz

Download URL adobepy-0.11.2.tar.gz
Size 80.2 kB
Tags Source
SHA-256 checksum
How to use checksums
eeb0e16109dc6111b03532c8ab44a0e72e5186dc12684dfb80ba81ae733fd5cb
BLAKE2b-256 checksum
How to use checksums
a24b97a6d8e70d07fa23937216de643504a9dd7ecc9f7ace77780382e699e231
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

Release files / adobepy-0.11.2-py3-none-any.whl

Download URL adobepy-0.11.2-py3-none-any.whl
Size 89.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c62275af62d71cc0cdbba5d01fabbabb6c9858db82e91430ccb1111035a8bb2a
BLAKE2b-256 checksum
How to use checksums
4c6c1c70c9a3c921e99722274fde8e0a4a375c35b14fd2a0e7d04ef9e33c022e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

Security for adobepy 0.11.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for adobepy-0.11.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

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