Mac agent infrastructure

Best Byte AI

Native Swift control for Python agents on macOS.

SwiftPython Commercial packages a signed CPython worker sidecar, actor-isolated ProcessPool, typed remote handles, shared-memory streaming, reentrant callbacks, and VM-capable isolation into the runtime layer behind SiriusAgent and SiriusMsg.

Public runtime layer

Not a PythonKit wrapper. Not a demo harness.

Most Swift-to-Python bridges put CPython inside the app process and leave the product with one interpreter, one GIL, and one crash domain. SwiftPython keeps the fast in-process path, then adds a worker runtime for package-heavy agent work.

The public commercial package ships the runtime API, worker sidecar, VM worker scripts, entitlement templates, runnable examples, and integration docs that Best Byte AI products depend on.

Runtime fit

Choose the bridge that matches the product boundary.

SwiftPython Commercial is for Mac apps where Swift owns the product, permissions, signing, updates, and policy while Python runs package-heavy agent work behind an explicit runtime boundary.

In-process Swift bridge

PythonKit

Best for

Simple embedded Python calls from Swift.

Pressure point

The app still shares the interpreter, GIL, thread behavior, and crash domain.

SwiftPython lane

Keep the native Swift API, then move agent workloads into ProcessPool or VM workers.

Native binding stacks

pybind11, PyO3, JEP

Best for

Hand-built native bindings around Python or CPython-adjacent code.

Pressure point

They do not package a Swift-owned worker pool, Mac sidecar, callbacks, and product distribution surface.

SwiftPython lane

Typed handles, callback channels, generated Swift-facing APIs, and signed Mac runtime artifacts.

Python-native execution

multiprocessing, Ray, Dask

Best for

Python-first parallelism, clusters, task graphs, and distributed compute.

Pressure point

Python owns orchestration; Mac apps still need lifecycle, policy, handles, and distribution discipline.

SwiftPython lane

Actor-isolated ProcessPool control with warmup replay, bounded respawn, events, and Swift-side ownership.

Service boundary

gRPC and generic RPC

Best for

Network services with well-defined request and streaming contracts.

Pressure point

RPC alone does not give Swift Python object handles, GIL-aware callbacks, or local shared-memory streaming.

SwiftPython lane

Local IPC designed for Python objects, stream events, progress, keepalive, and reentrant callbacks.

ProcessPool substance

A runtime shaped around the failure modes real Mac agents hit.

01

Remote Python Objects

PyHandle and OwnedPyHandle let Swift hold references to Python objects that live in worker processes, with generation tracking and stale-handle safety instead of pretending remote objects are local values.

  • Long-lived Python state
  • Owned handle cleanup
  • Handle-compatible APIs
02

Resilient ProcessPool

PythonProcessPool runs Python work in separate worker processes, so CPU-bound packages and native extensions do not inherit the host app's entire crash surface.

  • One GIL per worker
  • Quarantine and respawn
  • Warmup replay
03

Streaming IPC

The pool moves beyond request-response calls with binary-framed IPC, side-channel setup, stream events, progress, out-of-band buffers, and callback paths that Python can use to call back into Swift.

  • evalEvents streams
  • Shared-memory buffers
  • Sync and async callbacks
04

Mac Distribution

The runtime is packaged for applications: binary framework, sidecar worker, VM worker scripts, entitlement templates, examples, app-bundle guidance, and the preflight docs needed to ship it.

  • SwiftPythonWorker
  • SandboxPool
  • VM tenant support

Runtime boundary

The app owns trust. The runtime owns execution.

Native Mac host

SwiftUI and AppKit product surfaces, local sockets, permissions, signing, notarization, login items, and user-facing controls.

SwiftPython runtime

Actor-isolated pool management, handles, streams, callbacks, events, and generated Swift wrappers over Python packages.

Python workers

Sidecar processes or VM tenants that run package-heavy code away from the host app's permission and crash boundary.

Shipping proof

The runtime is already under real products.

SiriusAgent and SiriusMsg use the same product rule: keep privileged Mac behavior native, and run agent logic through explicit SwiftPython boundaries.

Public package

SwiftPython Commercial

The binary package for app builders: runtime XCFramework, worker sidecar, VM scripts, entitlement templates, examples, and API guide.

Use the runtime package
SiriusAgent icon Native agent host

SiriusAgent

A Mac agent host built on SwiftPython for providers, tools, browser work, memory, sandboxing, and local execution.

Read the runtime boundary
SiriusMsg app icon Public release

SiriusMsg

A signed local Apple Messages bridge for AI agents with explicit allowlists, a background agent, local service boundary, and signed update feed.

View SiriusMsg