Quick Start¶
A working agent, the web GUI, and your first chat — in under five minutes.
Soulacy is a local-first agent operating system: Studio for authoring and self-healing agents, Channels for delivery, Schedule for cron, Learning for making the same mistake less often, Packaging for versioned installs — all in one binary, all local by default.
1. Install¶
More options (Docker, VPS, launchd service): Installation.
2. Run the onboarding wizard¶
The wizard creates or updates your workspace (~/.soulacy/soulspace — the
soulspace layout), asks which LLM provider to
use, can wire web search and a starter agent, and can configure the release
manifest used by sy update check. Use sy setup only when you want to write a
fresh config from scratch.
No API key? Use Ollama.
If you run Ollama locally, pick it in the wizard and Soulacy works fully offline — no cloud account needed.
3. Start the gateway¶
The gateway starts on http://localhost:18789 with the full web GUI: Dashboard, Studio, Agents, Chat, Workboard, Knowledge, Memory, Skills, integrations, and observability. Take the GUI tour.
4. Talk to an agent¶
Open http://localhost:18789 → Chat → pick your agent → say hello. Watch the Thinking section show reasoning steps and tool calls live.
5. Make it yours¶
An agent is one YAML file. Open Agents in the GUI (or edit ~/.soulacy/soulspace/agents/assistant/SOUL.yaml):
id: assistant
name: Assistant
trigger: channel
llm:
provider: ollama # or openai / anthropic / google / any OpenAI-compatible
model: llama3
system_prompt: |
You are a helpful, concise assistant.
channels:
- http
Changes hot-reload — no restart. The full schema (tools, memory, reasoning, schedules, workflows) is in the SOUL.yaml reference.
6. Five things to try next¶
- Generate an agent from plain English — open Studio, describe the
automation, hit Generate (Streamed by default streams the pipeline
phases live below the canvas; the Wizard variant lets you step through
clarify_intent → choose_strategy → build_graph → validate → repair). Pick a Runtime intent preset (Fast local / Reliable local / Cloud quality) in the Studio model modal to bake sensible timeouts into the agent. → Studio - Give it skills — add the public skill directory and install one: Every install passes a security review before you consent. → Skill sources
- Put it on Telegram — a bot token and two YAML lines. The Channels page has inline guided setup cards for Telegram / Slack / Discord / WhatsApp / email / Teams / Google Chat, with per-field hints and a Test-delivery button that returns a friendly Diagnose reason on failure. → Channels
- Schedule it — run every morning, with automatic catch-up after
downtime. If the gateway missed a fire, the Automations row shows a
⟳ auto-replayedchip and Activity emits aschedule.missed_run_backfilledevent so you can tell "why did this fire at 03:04?" apart from a normal cron. → Schedules - Install a versioned package —
sy pull <owner>/<repo>or import via Agents → Import. The package v2 schema uses namespaced ids (owner/name), calendar versioning (2026.7.15), and an install-time secret gate that refuses to import if a required provider / channel / secret / MCP server is missing (with an "I understand — import anyway" opt-out for local experiments). → Packaging
Where everything lives¶
| Workspace (agents, skills, data) | ~/.soulacy/soulspace/ — layout |
| Config file | config.yaml in the workspace — reference |
| GUI | http://localhost:18789 — tour |
| CLI | sy — reference |