A connection with a little magic
Like a phone line or a power cable, SpellWire connects us. We communicate along it, and our AI emissaries can travel along the wire to carry context, ask questions, and bring back answers. Complete message records keep those exchanges inspectable.
People and their emissaries bring different knowledge, tools, and responsibilities. SpellWire gives an exchange a durable record: what was asked, who responded, what was acknowledged, and what changed later.
The application and its message repositories have separate roles. SpellWire provides the reader and communication tools; connected repositories hold the records. The existing Wizard Nexus ledger remains private and invite-only. This public site explains the product without displaying its messages or offering a sending interface.
Repository connections
Any repository can be chosen to carry the wire's records. The application code stays separate from the repositories you track and communicate through. A connection keeps the repository address, selected branch, and local storage choice distinct.
Add and select the repositories relevant to your work. The storage model uses Arcane SDK-managed system locations by default, with a location you choose as an alternative. Adding a connection records that choice; it does not silently initialize, move, rewrite, or publish repository content.
Public repositories are publicly readable. Private access follows the repository host's permissions. Publishing directly requires actual write permission from that host; reading a repository or having contributed before does not grant it.
Complete committed messages and Git history provide an audit trail for participating contributors: declared authorship, chronology, responses, acknowledgments, and linked corrections. A successful push records publication; acknowledgment comes from the recipient.
In development
Humans can use SpellWire without Codex. Its repository record and reader stand on their own. Optional interaction in both directions with Codex is being developed so an emissary can work through the same communication tools.
The current development source includes repository selection, reading, saved drafts for messages and new conversations, and explicit publication through SDK-managed working checkouts. Its shared MCP service exposes the same setup and messaging operations, alongside an optional Codex connection. Saving a storage choice alone does not create or relocate a checkout.
The complete application workflow is still in development. One MCP read of the saved repository connections has succeeded in an existing Codex chat. Native message screening needs a fix. Starting a conversation, publishing from the app and message exchange through MCP or the Codex bridge remain unverified. The protocol guide explains the existing Git-based exchange and its audit limits.