Skip to main content

vitruvian-tool-kit

Write a tool for the Vitruvian Mac app in Python. A tool is a folder with a vitruvian-tool.json and a program; the app starts the program and talks to it over its standard input and output. This kit is that conversation: you say what each command does, and call the app from inside a command as an ordinary function call.

from vitruvian_tool_kit import Tool

tool = Tool(version="0.1.0")


@tool.command("hello")
def hello(app):
    app.notify.hud(icon="hand.wave", message="Hello")


tool.run()
  • One call per message. app.notify.hud(...), app.clipboard.read_text(), app.storage.get(key=...): each is one request of the protocol, named as the protocol names it. The app may refuse any of them; the call then raises Refusal. Raise CommandRefused("why") to refuse a command yourself.
  • Synchronous, on one thread. A call to the app waits for its answer, ten seconds at most. A handler must not be async.
  • A tool can draw. With "protocol": "2" and panels in its manifest, tool.panel("counter", on_open=..., on_event=...) says what a panel shows and what each thing the person does gives; a page is tree(heading("Counter"), button("add", "Add one")), one function a kind of block. The handle sends a page unprompted with render and sets the tool's badge with badge.
  • A status, and a choice. app.status("busy", text=..., icon=...) sets the small mark the app draws on the closed island, for a tool whose manifest declares contributes.status. choice(id, value, options) is a pop-up menu on a page. Both are newer than protocol 2 itself: app.supports(Feature.CHOICE) says whether this app has one. On an app from before them app.status sends nothing and returns False, and a choice is drawn as its fallback text, so send a field there instead.
  • Never print. Standard output is the link to the app. Write to standard error, or call app.log(message=...).

Shipping it

The app starts a tool with Apple's python3 (/usr/bin/python3, Python 3.9), which has none of your packages. So the kit goes inside the tool's folder, and the program finds it there:

python3 -m pip install --target lib vitruvian-tool-kit
import os, sys

HERE = os.path.dirname(os.path.realpath(__file__))
sys.path.insert(0, os.path.join(HERE, "..", "lib"))

vitruvian-tool init --template python-kit writes a tool set up this way. The kit needs nothing but the standard library and Python 3.9 or later.

The whole guide, the protocol and the other kits are in the SDK. MIT licence.

Metadata

Release files for vitruvian-tool-kit 1.3.0

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

Source distribution (sdist)

Source distribution for vitruvian-tool-kit 1.3.0
File Size Uploaded
vitruvian_tool_kit-1.3.0.tar.gz 37.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for vitruvian-tool-kit 1.3.0
File Interpreter ABI Platform
vitruvian_tool_kit-1.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 75.4 kB

Release files / vitruvian_tool_kit-1.3.0.tar.gz

Download URL vitruvian_tool_kit-1.3.0.tar.gz
Size 37.4 kB
Tags Source
SHA-256 checksum
How to use checksums
dccdac31d1923d6abba33d0e18baa11becea6494897a582ee0409bd731ca7b6a
BLAKE2b-256 checksum
How to use checksums
9597ca46dc8901c06b29265c22b4fc454246b2b94663479147afa1dec15d87fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

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 14, 2026.

Transparency log

Release files / vitruvian_tool_kit-1.3.0-py3-none-any.whl

Download URL vitruvian_tool_kit-1.3.0-py3-none-any.whl
Size 38.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
79a46024fd55987bc3b26392cb98add58fcb4067b10da51e231384e7034acb39
BLAKE2b-256 checksum
How to use checksums
7cacc6bf090b4787002d0f40bec6c8212170ca85955b2797935bb36ecb7a3b73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

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 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.3.0 This release

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.10.0

2 release files

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