✳ Open source.
Runs on your machine. No platform lock-in.
YOUR STACK / YOUR RULES
your agentYOU'RE IN CONTROL
⌂
Agent HomeIdentity, with history.
↔
MessagingOne less open terminal.
✳
Agent ForgeNext on the horizon.
⑂
Model RouterWatch this space.
EST. FOR THE BUILDERS
Fast.Less baggage.No BS.SMALL TOOLS. BIG POSSIBILITIES.
↗
01 / THE LINEUP
Not another walled garden. A set of
open doors.
Start with one tool. Connect another when you need it. Each project
has its own job, its own source, and a place in your stack.
⌂ EARLY PROJECT
THE FOUNDATION
Agent Home
A home for more than a prompt.
Keep your agent's identity, instructions, memory, skills, and
runtime configuration together. Local Git history makes changes
yours to track and restore.
Part of the growing Soulsteads family. The public repository is
reserved; a public implementation, feature set, and setup guide
have not been published yet.
A future member of the lineup. Its public repository is reserved.
Routing capabilities, supported providers, and installation
details are not yet published.
Home manages the agent's files. Messaging handles the chat
connection. Your chosen runtime does the work. No all-or-nothing
framework.
⌂
THE PLACE YOUR AGENT CALLS HOME
Familiar files. Not a new platform.
Agent Home launches your chosen runtime from a directory you
own. Edit the Markdown, add local skills, and keep a history you
can inspect. No remote is added automatically.
uv tool install git+https://github.com/soulsteads/soulsteads-agent-home.git
soulsteads create helper --runtime opencode
soulsteads run helper --dry-run
soulsteads run helper
AGENT MESSAGING
Take it out of the terminal.
Paste this into your coding agent to start setup. Linux Telegram
setup is guided for Claude Code and Codex; other connectors
require manual configuration.
Set up Soulsteads Agent Messaging.
Clone https://github.com/soulsteads/soulsteads-agent-messaging
using the release branch. Read README.md and docs/SETUP.md.
Ask which chat app and runtime I want.
Keep tokens in a private file, never in chat.
Ask before starting a service or changing anything outside the checkout.
Tell me how to test the connection.
05 / STRAIGHT ANSWERS
Good questions. No fine-print maze.
Open tools should come with clear boundaries. Here's what you're
getting—and what you're not.
Do I need the whole stack?+
No. Use Agent Home directly with a supported runtime, use
Messaging without Home, or combine them. Neither installs or
configures the other automatically.
Is this a hosted AI service?+
No. These are tools you run on your machine. You bring your own
runtime, model access, chat accounts, and credentials. Your model
and messaging providers' costs and privacy policies still apply.
Is my agent sandboxed?+
No. Home and Messaging do not sandbox your agent. It keeps its
machine permissions. Keep secrets out of tracked files. Telegram
is not an end-to-end-encrypted path to your machine, and
Messaging's Matrix encrypted replies are not yet
interoperability-qualified.
Can I cancel a remote task safely?+
Messaging's /cancel is not a kill switch. A shell process can keep
running in the known Codex cancellation case. Unattended remote
command execution is not qualified; review the Messaging README
before connecting a powerful agent.
Can I bring an existing Hermes agent?+
Agent Home has an optional Hermes importer. Inspect an explicitly
selected source first; applying creates a fresh home, not a live
messaging cutover. Unsupported settings are reported, and
incomplete imports need acknowledgement.
Read the import guide.
Where are Forge and Model Router?+
Their public repositories are reserved. They are previews, not
installable releases, and no public feature contract is published
yet. Follow their repositories for future updates.
Is Soulsteads open source?+
Agent Home and Agent Messaging are published under Apache 2.0.
Read the source, report a bug, or propose a change. Preview
projects will publish their own licensing and setup details when
available.
soulsteads