Assistant
In development
Apache-2.0
Bailey
An open-source AI assistant that runs ready-made solutions on your own machine, with your own AI key.
Getting AI to do one real job reliably is still a project: someone writes the instructions, connects the tools, supplies the documents and the keys, and keeps it all working when something changes. Bailey is being built to run solutions instead: complete, versioned packages for one job, installed in one step, that ask only for the keys they need and ask before any tool changes something, on your machine and with the AI provider you choose. It is built in the open from its first release, which checks that a machine has what the assistant will need. Solutions will come from anywhere, since they are open formats, and from Sigrix, where the people who build them sell them.
Repositorysigrix-io/bailey
Packagebailey · PyPI
LicenseApache-2.0
RequiresPython 3.11+
Installuvx · pipx
uvxbaileydoctor
Specification
v0.1 · draft
Apache-2.0
Postern
The open execution and entitlement protocol for packaged AI agents.
You bought or downloaded an agent. It is a folder on your machine. Now what? Today the answer is different for every agent, so every client that wants to offer something nicer than a terminal has to hard-code that knowledge per agent — which means nobody does it. Postern fixes the interface, not the agent: four HTTP verbs an agent serves, and a licensing check the packaging standards leave as metadata only.
Repositorysigrix-io/postern
Specification0.1 · draft
LicenseApache-2.0
Complete impl.sigrix-runtime · Level 3
InstallDocker · pip
describerunstreamstatus
Browser client
Postern v0.1 · draft
Apache-2.0
Gatehouse
A browser client for Postern: the page a person runs an agent from, for any runner that serves the four verbs.
Given a runner's describe and status documents, Gatehouse draws a form for its inputs, a run button, the steps as they happen and the result with what the run used, then connects the page to the four verbs over fetch. Beside that page it draws an app's card, a run history and a usage summary from a host's own data, for a page of several apps, and what is inside a playbook from its playbook.json. It holds nothing else: six scripts and a stylesheet, with no build step, no runtime dependency and no second origin. Nothing an agent returns is ever parsed as HTML. It draws the buyer's run page, the seller's preview, the admin preview and a playbook's contents on Sigrix, and became a package of its own once Bailey needed the same page for a solution's apps.
Repositorysigrix-io/gatehouse
Package@sigrix-io/gatehouse · npm
LicenseApache-2.0
Requiresa browser · a Postern runner
Installnpm · or copy src/
postern_client.jsrun_view_model.jsrefusal_copy.jsrun_renderer.jshost_blocks.jsplaybook_contents.js
MCP server
Seller API v1
Apache-2.0
sigrix-mcp
Publish prompt, persona, skill, MCP server and assistant listings to Sigrix from the AI client you already write in.
Authoring a listing and publishing one happen in different places: the writing is done in Claude Code, Claude Desktop, Cursor or VS Code, and then re-typed into a web form. This is the second half, handed back — an MCP server that takes a draft from a sentence to the review queue without a browser. It is deliberately thin: no model of its own, no copy of any rule, and no secret beyond your seller token. What submit would refuse it asks Sigrix and repeats verbatim, and nothing it can reach publishes anything — a submission is queued for moderation exactly as one made in the wizard is.
Repositorysigrix-io/sigrix-mcp
Packagesigrix-mcp · PyPI
LicenseApache-2.0
RequiresPython 3.11+ · a seller token
Installuvx · pipx
list_categorieslist_my_listingsget_listingcreate_draftupdate_draftcheck_draftsubmit_for_reviewimport_skill_mdexport_skill_md
Launcher
Postern v0.1 · draft
Apache-2.0
sigrix-launcher
Start an MCP server you bought on Sigrix from the client you already use.
Some listings are a seller's own software, delivered by Sigrix rather than published anywhere: a package only its buyers can download. This is what a buyer's MCP client starts for one. On every start it asks Sigrix whether your token owns the listing, downloads the seller's package and verifies it before anything is written, installs it into an environment of its own once per version, and hands your client's stdio to the seller's server. The purchase check and the download are sigrix-runtime's own client code, and neither package needs anything beyond the Python standard library.
Repositorysigrix-io/sigrix-launcher
Packagesigrix-launcher · PyPI
LicenseApache-2.0
RequiresPython 3.11+ · your Sigrix token
Installuvx · pipx
uvxsigrix-launcherrun<seller>/<listing-id>
Runner
v0.1.0
Apache-2.0
sigrix-runtime
The Postern runner inside every bundle Sigrix delivers: the four verbs and the licence check, on the buyer's own machine.
Every agent a buyer downloads from Sigrix carries this package. It serves the agent's describe, run, stream and status on loopback, asks the distributor whether the buyer's token still owns the listing before it runs anything, and can serve an MCP server's tools over the same four verbs. The server needs nothing beyond the Python standard library, so it answers before anything is installed; a CrewAI crew runs through it once its extra is. It was a directory in the Sigrix repository until it became a package of its own, and the version this row reads is the one every bundle built here carries.
Repositorysigrix-io/sigrix-runtime
Packagesigrix-runtime · PyPI
LicenseApache-2.0
RequiresPython 3.11+
In use here0.1.0
Installin every bundle · pip
posternexecutionworkforceloaderconfigurationsandboxquietrunner_env
Library
v0.2.2
Apache-2.0
mullion
One correct way to open an image: EXIF orientation applied, transparency resolved rather than dropped.
Every picture anyone hands this platform — an avatar, a storefront cover, a sample render — is opened, fitted, sometimes marked and re-encoded by this library. It exists because the defect it prevents is invisible: each upload path decided orientation and transparency for itself, they reached different answers, and the wrong ones stored a cutout on a black rectangle behind a 200 response and a picture that renders. It was a module in the Sigrix repository until a second codebase needed exactly it, and it has no marketplace in it: what the watermark says is ours, drawing it is not.
Repositorysigrix-io/mullion
Packagemullion · PyPI
LicenseApache-2.0
RequiresPython 3.11+
In use here0.2.2
Installpip
sourceresizewatermarkencodebackgroundpage
Tool
v0.2.0
Apache-2.0
Herald
One announcement to every channel you choose: each text fitted to its platform, shown before it is sent, and posted once.
Herald posts an announcement to Bluesky, Mastodon, Discord, Slack, Telegram, a LinkedIn profile or page and X, from one command, a feed it watches, a GitHub Action, an assistant over MCP or a Python call. It counts each channel's text the way that platform does and refuses a post that is too long rather than cutting it, shows exactly what each channel will get before anything is sent, then posts that draft and keeps a ledger, so the same announcement is never posted twice. The Hub announces each update through it, with Herald's ledger kept in this platform's own store. Nothing in it is specific to Sigrix, and it needs nothing beyond the Python standard library.
Repositorysigrix-io/herald
Packageherald-post · PyPI
LicenseApache-2.0
RequiresPython 3.11+
In use here0.2.0
Installpip · uvx
announcementdraftscountingchannelspostingledgerfeedsmcpclihttp
Format
v0.1
Apache-2.0
Muster
The playbook format: one playbook.json that says what each file is for, the order a person works through them, and the placeholders a buyer fills in.
A playbook is a process a business runs by hand, sold as the files a person works through: the steps, the copy to send, the checklists and the tools that work offline. Muster is the document beside them, with a JSON Schema at a permanent address and a table of cases, valid documents and invalid ones each made by one change, that every implementation runs. Its README states the rules no schema can: every file named is in the folder, every placeholder used is declared, and an HTML file loads nothing from the network. Sigrix checks every playbook uploaded to it against the format and Gatehouse draws what one holds; anyone can write a playbook, and check its playbook.json against the schema, without either.
Repositorysigrix-io/muster
Format0.1
LicenseApache-2.0
Schemaplaybook.schema.json · served here
Cases4 valid · 35 invalid
format_versionnametitleorderfilesslotsexamples_are_fictional