szpont
Install-and-run for Diplomat (Szpont Yon) - the menu-bar / system-tray applet that reviews your pull requests, fixes your own, resolves conflicts, and keeps one device per agent.
pip install szpont && szpont # or: npx szpont
That is the whole install. macOS and Linux.
What it actually does
Diplomat is built out of the checkout it runs from - a SwiftUI bundle on macOS, a
PySide6 package plus the diplomat-core Swift binary on Linux - and it keeps
being that checkout: the Update button, the daily 06:00 timer and the commit the
panel reports are all git operations on it. A wheel holding a copy would be a
second Diplomat that no update could reach.
So this distribution is the steps in between, and every one of them runs a script that is already in the repository:
| macOS | Linux | |
|---|---|---|
| get it | git clone into ~/.diplomat/checkout, or fast-forward it |
same |
| build it | install/build-app.sh → Diplomat.app |
install/build-core.sh when the prompt binary is missing |
| set it up | - | a venv at ~/.diplomat/venv with requirements.txt in it |
| start it | open Diplomat.app |
the package's own ./diplomat, on the venv's interpreter |
Nothing is rebuilt that does not need to be: a venv is left alone until
requirements.txt changes, and the Swift prompt binary is only built when the
applet would not find one. git is needed to fetch Diplomat, and a Swift
toolchain to build it - if one is missing you are told which and where to get it,
before anything is downloaded.
szpont --plan # print what would be run, as JSON, and do none of it
szpont --no-update # launch the checkout as it stands
szpont -- --dump # everything after -- goes to the applet
DIPLOMAT_SELF_REPO points at a checkout of your own - the same variable the
running applet reads, and one this launcher never updates, because a working copy
may have work in it. DIPLOMAT_REPO_URL clones from a fork.
The same name on both indexes
npx szpont runs the same launcher, and that is all either name installs: one
file of standard library on each side, no dependency on either index. What keeps
them one command is packages/szpont-npm/test/parity-with-python.mjs - every
machine shape in test/scenarios.mjs goes through both planners, and the two
answers have to be identical.
The protocol Diplomat's machines find each other over is
SzpontNet,
published separately as szpontnet; nothing here imports it, and installing this
does not install it.
Its own tests
pip install pytest
pytest packages/szpont/tests -q
Note on the name
szpont names three things, and they share the namespace rather than compete for
it: this command, its npm twin, and the
conformance tester,
run as python -m szpont from its own directory.
Only the tester is precarious. It is never installed, and the working directory
precedes site-packages on sys.path, so it wins from where it is run - but
publishing it under this name is what the three could not share. The console
script cannot collide with it at all: an entry point is a file in bin/, not a
name on the import path, and the module this one lives in is szpont_launcher.
1 maintainer
Metadata
1 maintainer
Release files for szpont 0.85.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| szpont-0.85.0.tar.gz | 14.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| szpont-0.85.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.5 kB
Release files / szpont-0.85.0.tar.gz
| Download URL | szpont-0.85.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed3e15be2f8c30fbc4d51e5cd1c08d2fdc6963e6e97e2d1e4047a82b0d36eca7
|
|
BLAKE2b-256 checksum How to use checksums |
abdbbe4cf18ca6e93496400aff28d6a9768940e0e4d47f91441095e48d1ce5c8
|
| 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 9, 2026.
Transparency logRelease files / szpont-0.85.0-py3-none-any.whl
| Download URL | szpont-0.85.0-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
328a6dfb66f1aedef3766ba3624d43c8b00703520a2bbe0610426149f6af620f
|
|
BLAKE2b-256 checksum How to use checksums |
b0779f6f8bbdce4d2b7cb48ceaf41f0d9b5cb88733ca8497729576efef47f123
|
| 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 9, 2026.
Transparency logSecurity for szpont 0.85.0
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for szpont-0.85.0.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 9, 2026.
Transparency logA 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.
