A home at the edge of the known: Voidstead is being built to hold your work and the memory your model needs.
Voidstead is designed as a home for your work
An agent harness: refusals that say why, credentials kept from the model, memory integration underway, vendor-neutral files on your disk.
Voidstead’s workbench sets declared boundaries for your model’s work
Memory is being built in; including our method for designing automations is planned, so you could build workflows.
The workbench refuses capabilities that cannot run safely. Voidloom is the memory we already work with. Its integration into Voidstead is being built; in testing, recall worked with the network closed. We use the automation design method in our own work.
Your home, drawn to show what each part is for.
Voidstead’s home and its parts appear as lantern lights around a flame. Voidstead is in development; these are the parts it is designed to hold. This is our drawing, not a view from inside Voidstead.
What the parts do for you
- Safe work on your machine: Voidstead refuses work that cannot run safely on your machine and tells you why.
- Credentials beyond the model’s reach: Voidstead keeps your credentials out of the model’s reach, within declared limits.
- Network closed by default: The model’s listed address is the only permitted destination for its requests.
- Your work in vendor-neutral files: Your work stays on your own disk by design.
- Your home: The home is for your knowledge, your agents, and their memory on your own machine.
- Agent memory: Voidloom would be the home’s memory; in testing, recall worked with the network closed.
- The model you choose: Model connections are for the hosted or local model you choose.
- Approval for network openings: This is how you would approve an opening beyond your model’s listed address.
- Knowledge from your documents: Voidmill turns documents into knowledge and would have an optional place in Voidstead.
- Help getting started: Setup would include a guide, help with outside connections, and a machine check.
- Questions before costly guesses: Voidstead would use what it knows of your work and ask only when a wrong guess would be costly.
- Designing your own automations: Our method for designing automations would help you design your own in Voidstead.
- Extensions for your work: An extension would bring skills and automations for a kind of work into your home.
- Knowing your model’s limits: The check would measure your model and explain which features stay locked and why.
Voidstead’s design keeps your work in vendor-neutral files
The model is a replaceable connection; it does not hold the value of your work.
Your work is also kept apart from what Voidstead itself provides. An upgrade replaces only what Voidstead provides, leaves your work as you left it, and can be rolled back.
Voidstead is designed for the model you choose
The agent home is being built for hosted models and the open models you run on your own machine.
In testing, adding another provider required no changes to existing code. Voidstead has not yet been run with a live provider.
Voidstead refuses what cannot run safely on your machine and says why
Each refusal explains what blocked a capability and what would permit it; everything else runs, with missing capabilities named.
Credentials stay outside the model’s reach, within declared limits. By default, the network is closed to outbound connections. Requests to a hosted model you choose may go only to the provider address Voidstead lists for it, with each connection recorded. No request has yet reached a live provider. A local model’s requests stay on your machine. Any other opening made for the model’s work would be for one host, state its purpose, and expire. The step in which you would approve such an opening is planned.
Voidstead is designed to explain which features your model can run
The capability check is designed to enable only what the chosen model can perform reliably.
The check would explain each locked feature and its reason. It has not yet been run against a model.
You could build your own extensions without changing Voidstead itself
Planned extensions could cover, for example, the work of building and caring for websites and resource hubs, or of marketing.
Working with us could happen in either direction: Andrew could lend Voidstead as the harness for someone’s product, or a collaborator could build an extension that brings their work into the home.
An extension would bring a kind of work into the home and use the home’s own parts.
Extension examples appear as their own structures beside the home, drawn from our work. Voidstead is in development; these are the parts it is designed to hold. This is our drawing, not a view from inside Voidstead.
In testing, adding and removing an extension left the home and your work untouched.
What extensions could add
- Web development: It could bring skills and automations for building and caring for websites and resource hubs.
- A website’s purpose: The extension’s skills could help decide what a website is for before building starts.
- A site’s look and structure: The extension could include skills for shaping a website’s look and structure.
- From design to website: Automations in the extension could turn a website’s design into the site.
- Words for your website: The extension’s writing skills could help create the words for a website.
- Checks before opening: The extension’s automations could check a website before it opens to visitors.
- Ongoing site care: The extension could help care for a website after it opens.
- Marketing: An extension could bring go-to-market strategy skills and automations into your home.
- Research for your strategy: Research into markets, competitors, and audiences could guide your strategy.
- Your positioning and message: Market and audience research could shape your positioning and messaging.
- Content across channels: The extension could create content for every channel and check sources before release.
- Ads for your audience: The extension could create paid ads carrying your positioning and message to the intended audience.
- Publishing across channels: The extension could publish reviewed content across channels within the same go-to-market strategy.
Your work would have one central place
Voidstead is designed so your agents, their memory, and your knowledge would live together on your machine. Remote control and fast decisions are planned as options you would turn on.
Questions about Voidstead
What is Voidstead?
Voidstead is an agent harness being built as a home on your own machine, where you could build workflows and automations with the model you choose; no live provider has been tried yet. It already refuses what cannot run safely on your machine and keeps credentials from the model. Its memory is being built in.
Who is Voidstead being built for?
Voidstead is being built first for people who already use AI at a moderate to advanced level and want to build it into what they make. Making Voidstead easy for people who are not AI engineers comes after a working version.
Would the memory and document tools still need separate assembly?
No. Voidloom, the memory we rely on, is being built into Voidstead. Voidmill, our working document tool, is planned as an optional addition whose absence would break nothing.
How is work kept separate from model choice?
By design, everything of value stays in vendor-neutral files on your disk, not inside the model.
Would Voidstead require a single model provider?
No. Voidstead is designed to accept models from any provider, hosted or local; that scope has not been tested with live providers.
Is the workbench absolutely safe?
No. Voidstead applies execution, credential, and network controls with declared limits.
Does Voidstead’s capability check choose the model automatically?
No. Voidstead’s capability check is designed to test the model you bring.
Can workflows be built in Voidstead today?
No. Building workflows on Voidstead is not possible yet. Our method for designing automations is planned to join Voidstead, as are extensions, so people could then build their own.
A stead holds everything needed to keep going. Voidstead is designed to be that holding for your work.
In development. A private build, not yet available.
Voidstead is being built for Linux, and for Windows through the Linux environment built into Windows. A native Windows version is not planned.
What it does not do ·
- The complete agent home is still being built. Building workflows there is not yet possible.
- Hosted and local model connections have not yet been tested with live providers. The capability check has not yet been run.
- Voidloom integration is still being built. As of , Voidloom’s background thinking runs on the hosted or local model chosen at Voidloom’s own setup, if any. With a local model, research into gaps in what Voidloom knows is skipped because that research needs the web.
- Adding Voidmill for documents is planned as an optional feature.
- A teaching guide, guided outside connections, and first-run machine checks and model selection are planned.
- Filling in known work context and asking only when a wrong guess would be costly is planned.
- Extensions are planned, so people could extend it. Including our method for designing automations is planned, so they could design their own workflows.
- The intended experience for people who are not AI engineers remains mostly planned.
- No one has yet reconstructed what an agent did from Voidstead’s record alone.
- There is not yet a step for approving a network opening beyond the chosen model’s listed address.
- Voidloom’s memory is not yet connected to the work a model would do in Voidstead.
Thank you. We will email you when there is news about Voidstead’s availability.
Thank you for sharing.