Salsa

Quickstart

Get up and running with Salsa in 5 steps. From daemon start to autonomous execution in under 5 minutes.

Start the Daemon

Run ./executive-os start to launch the background service. The HTTP API starts on port 3000, WebSocket on 3001, and the web UI on port 4000.

Complete Onboarding

Open localhost:4000 and walk through the setup wizard: pick account type, verify email, reserve your org name, set display name, and connect a provider.

Connect a Provider

Bring your own key (BYOK) from OpenRouter, Anthropic, OpenAI, or Groq. The Smart Router automatically tiers requests: Fast (local), Standard (Haiku), Frontier (Opus).

Create Your First Issue

Navigate to your team board and create an issue. Describe what you want built, researched, or analyzed. Use comments to refine acceptance criteria.

Dispatch It

Hit Dispatch on any issue. Salsa generates a plan DAG, runs QA review, then executes each step in the sandbox. Watch progress in real-time.

Visual Discovery Journey

Salsa's interface is designed for real-time visibility into agent reasoning and autonomous system health.

1. Intelligent Alerts (Guardrails)

Located in the top header. A glowing amber notification appears when a Plan is 'Blocked' (e.g., SAL needs a decision or JOY needs credentials).

2. Account & Brain Health

Access via Profile (Bottom-Left) -> Settings -> Account. Manage your Google AI Ultra tier, marketing emails, and neural telemetry.

3. Plan DAG (The Storyboard)

Located in the Plans view. A visual graph shows how an Issue is decomposed into parallel research and execution nodes.

4. Focused Collaborator

The Issue detail view provides a workspace-like focus for a single deliverable, keeping conversation and output linked to the goal.

5. Cortex Neural Stats

Located in Settings -> Monitoring. Real-time loss/gradient graphs showing how the local Executive Brain is learning from your workflow.

Core Concepts

Salsa is built on four fundamental pillars that ensure precision and reliability.

The Brain

The central orchestrator that manages state, routes commands, and ensures all 'organs' of the system are synchronized.

AI Agents

Specialized workers that execute specific tools, perform research, and collaborate in real-time to solve complex tasks.

The Event Store

An immutable, append-only heart that logs every action and decision, enabling perfect auditability and state replay.

The Canvas

A visual playground for ideation and rough decomposition before committing work into tracked Issues and Plans.

Core Workflows

Board + Issues

Manage your workflow with a high-performance Kanban board. Each card is an 'Issue' that can be dispatched to specialized agents.

Plan Orchestration

Plans are directed acyclic graphs (DAGs) of steps. Salsa ensures dependencies are respected and providing a clear path to completion.

Comment-Driven AC (Acceptance Criteria)

You can update acceptance criteria directly from issue comments. Mention @salsa and provide numbered or bulleted criteria. Salsa will update the issue AC block and prompt you to Retry or run again so output artifacts reflect the new criteria.

Example"@salsa Update AC: 1) categorize spend by tech/real-estate/travel/personal, 2) split across owners, 3) mark tax-deductible, 4) include cost-segregation candidates, 5) add CPA questionnaire."

Pro TipAlways run 'QA' on a plan before approval. This allows a secondary agent to verify the proposed steps against your current codebase.

Architecture

Salsa uses a 'Micro-Database' architecture where each domain (Chat, Memory, Tasks, Knowledge) has its own isolated SQLite database. This maximizes concurrency and minimizes context window noise for agents.

exec-core: The Rust-based brain handling event sourcing and CQRS.
atlasd: The secure sandbox that executes agent code in isolated VMs.
GraphRAG: A hybrid search system using LanceDB and SurrealDB for high-dimensional institutional memory.

Troubleshooting

Agent Response Delays

If agents seem slow, check the 'Spend' dashboard to ensure your provider tier is sufficient for the requested concurrency.

WebSocket Disconnects

Salsa uses WSS for real-time events. If you are behind a proxy, ensure at least one of ports 3000-3001 is open for upgrades.

Glossary

Key terms used throughout Salsa.

Organization: Your top-level workspace. Contains teams, issues, and configuration. Reserved during onboarding.
Workspace: The local runtime environment where Salsa runs. Includes the daemon, databases, and sandbox VM.
Team: A named group with a unique key (e.g. ENG, OPS). Issues belong to teams. Each team has its own board and backlog.
Agent: A specialized AI worker that executes plan steps. Agents run inside the sandbox and communicate via DSP protocol.
Lock: A mechanism preventing concurrent modifications. Issues are locked during dispatch to ensure single-writer semantics.
GraphRAG: Hybrid retrieval-augmented generation using vector embeddings and knowledge graphs for institutional memory.
Plan (DAG): A directed acyclic graph of steps generated from an issue. Steps have dependencies, tool calls, and validation gates.
Dispatch: The act of sending an issue for autonomous execution. Generates a plan, runs QA, and executes in the sandbox.
Sandbox: An isolated virtual machine where all agent code executes. The moat that prevents uncontrolled system access.
Approval Gate: A checkpoint requiring human consent before execution proceeds. Plans must be QA'd then approved before running.

Live Feed

Syncing with latest documentation updates...