Skip to main content

furb-monty

The engine of furb for Python, run in monty, a Python interpreter written in Rust. Most programs do not import it directly: pip install furb installs it, and furb.open opens a life on it, as the examples show. Read on when you write a host of your own, which boots an engine on ears that you choose.

What it gives

  • furb_monty.engine gives every name of the contract, engine.pyi, over one life of the engine in the sandbox of monty. The crate loads the Kernel there, so this package needs none of its own.
  • furb_monty.gate is the gate of the crate. The package furb reads a word with it too.
  • furb_monty._monty is the door itself. It gives the same host API as the package of TypeScript, each name in the case of Python. Its Engine has one method for each verb of the contract, which takes the words that the verb needs by position and the others by name, and gives an Act when the verb makes one.

FURB_ENGINE=monty makes from furb import engine give furb_monty.engine. The suite of furb runs on both engines.

Open a life

_monty.opened(directory=..., record=...) opens a life as every host of the crate opens one. It gives the record and the ears of the crate, which the host boots after its own ears. Engine.open(ears, directory=...) boots them at once.

from furb_monty import _monty, engine

record, ears = _monty.opened(directory=".", record="life.jsonl", actor="anthropic:claude-opus-5-5")
# `world` is an ear of the host that answers the rest, a prompt to the operator among it.
root = engine.boot(record, world=world, **dict(ears))

The ears of the crate are the provider of the models, the extensions, the ear of each official extension, the files, the commands, time, and the store and the log when the life keeps its record. The extensions enable at the start what the configs of the user and of the directory turn on, unless extensions=False. Each ear is a NativeEar, which furb_monty.engine.boot takes beside the generators of this interpreter, and which the engine of this interpreter, furb.python, steps as a generator of its own.

The words of opened, each of which can be left out:

  • actor is the default actor, and roster the models that the provider offers beside it. With no roster, it offers each model of the catalog, and with neither, the first of them is the default actor. A roster that names no model offers the model of the actor alone, and with no actor, the operator alone. Models says how a model is named.
  • keeps false keeps nothing in the record, and inspecting true opens a life that keeps nothing, enables nothing new, and asks no model.
  • extensions false enables no new extension, and config names the config directory of the user.
  • snapshot false opens the life with a replay of its record, and keeps no snapshot of it.
  • answer, a function, answers each request in place of the models, as the suite of furb does.
  • stream, a function, hears what a model writes as it writes it, and retrying each retry of a call of a model.
  • log, a function, hears each report of the life that no model reads, one line each, in place of the stderr of the process.
  • claude names the claude command line to run, and stall how many seconds a turn of it may go with no progress.
  • images is the directory of the images that a message names.

Only the opening of a life makes the files of a record again in its scratch directory, and gives a life with no record a directory that goes with it. scratch(record) gives the scratch directory of a record, which a host removes when it deletes the record.

The parts one by one

  • models(claude) gives the models that the catalog of this machine offers, model(name) one model by its name, and levels() the levels of effort.
  • files(scratch), bash(scratch, record), time(), extensions(given), memory(config) and skills(config) give the ears one by one, as the suite of each extension boots them. store(path) gives the record that a path holds and the ear of its store, and official() gives the official extensions, which extensions takes. The files and the commands share the scratch directory that the host names, which a word reads as scratch:// and a command as $TMPDIR.
  • answered(shape, line) reads a line of the operator as a value of one of the shapes(), by the rules that every console of the crate reads a line by.
  • _monty.SYSTEM is the system prompt of every model: the engine, minified with its program kept as it is.
  • setup() says what a first run checks of each place of the models, parts(project) gives the part for the TUI of each extension, enabled(root) the extensions that a record enabled, and kept(path) the entries of a record. furb_monty/_monty.pyi gives each other name, with its types.

Work that waits

  • furb_monty.engine.pending() names each act that an earlier life left and that waits for a wake, as ("bash1", "bash").
  • furb_monty.engine.parked() names each run of a word or reply that a crash loop parked, which a wake does not run.
  • furb_monty.engine.retry(id) runs a parked act again.

A resumed life says which acts each one names.

Make an act once

furb_monty.engine.keyed(key, kind, *args, **kwargs) makes the act of a verb once for a key of the client, across a crash of the host and a retry of the client, as keyed("k1", "prompt", int, "count the lines", on=root). A key fact goes to the record before the act, and a later call with the same key on the same chain gives the act that the key made, in this life or in a later life on the record. When the host crashed after it kept the key and before it kept the act, the call makes the act.

Ears of this interpreter

boot takes a generator of this interpreter as an ear, beside the ears of the crate. A verb that it calls while it hears goes to the life that it hears.

Metadata

Release files for furb-monty 0.4.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 furb-monty 0.4.2
File Size Uploaded Provenance Actions
furb_monty-0.4.2.tar.gz 662.9 kB Without provenance Details for furb_monty-0.4.2.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for furb-monty 0.4.2
File Interpreter ABI Platform Actions
furb_monty-0.4.2-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for furb_monty-0.4.2-cp314-cp314-win_amd64.whl
furb_monty-0.4.2-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for furb_monty-0.4.2-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
furb_monty-0.4.2-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for furb_monty-0.4.2-cp314-cp314-macosx_11_0_arm64.whl

Total release size: 79.8 MB

Release files / furb_monty-0.4.2.tar.gz

Download URL furb_monty-0.4.2.tar.gz
Size 662.9 kB
Tags Source
SHA-256 checksum
How to use checksums
33447c4d25480010d120b6c557bf7fbcfdb25dd4c689b36b7b5cf5ba0880f132
BLAKE2b-256 checksum
How to use checksums
624bf6e25e938c7fe3571991ac9ed0abae6a36003058a5b808ad7c4a35d5885d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / furb_monty-0.4.2-cp314-cp314-win_amd64.whl

Download URL furb_monty-0.4.2-cp314-cp314-win_amd64.whl
Size 25.1 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
28836029e9f89a69977e074de578dd0404a1fb20e60da98db2abae666817b048
BLAKE2b-256 checksum
How to use checksums
e463dfcfbc26e82a70726848b259563088ee6b4ae8bf1b32338072440483c921
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / furb_monty-0.4.2-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL furb_monty-0.4.2-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 28.1 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
67d420c39b76f114659b6c602767f6b9b5a1c3cca836060eff64dc6a87755b71
BLAKE2b-256 checksum
How to use checksums
3a75a5ace52b1045736a13b094f87b8927b5d51a26311862c7db16d94e599e9f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / furb_monty-0.4.2-cp314-cp314-macosx_11_0_arm64.whl

Download URL furb_monty-0.4.2-cp314-cp314-macosx_11_0_arm64.whl
Size 25.9 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3ae9028024248b12df5942bbb3093f6507a9dff2a8eacb2865698e2ea4ba61b5
BLAKE2b-256 checksum
How to use checksums
6b53096521d4ccf32d6ad8b91156b57424eb6f782633df9a0ed7d6fe58d31553
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for furb-monty 0.4.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.

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