Overview
SynthHires Space (/space) is the full agent workspace: a chat surface with real-time streaming, a catalog of specialized agents, cross-session memory, a semantic knowledge base, visual pipeline orchestration, content generation, and full control over the models and API keys you bring yourself.
This page explains the mental model. Every section has its own reference page linked from the sidebar. If the AI vocabulary isn’t second nature yet, read AI concepts from scratch first — it defines tokens, context, embeddings, agents and the other ideas this workspace runs on, without assuming any background.
What the Space is
Section titled “What the Space is”The Space is a local-first agent platform running on Cloudflare Workers. The core promise is BYOK (Bring Your Own Key): your LLM API keys are encrypted locally with AES-256-GCM and never travel to our servers. The platform is the orchestration surface — the billing relationship stays between you and your model provider.
The workspace is organized into five areas:
| Area | Pages | What you do there |
|---|---|---|
| Sessions & chat | /space, /space/chats |
Run conversations, orchestrate agents, manage history |
| Resources | /space/agents, /space/skills, /space/prompts |
Pick agents, install skills, reuse prompts |
| Context | /space/memory, /space/knowledge, /space/artifacts |
Recall, RAG knowledge base, generated artifacts |
| Automation | /space/studio, /space/cron |
Visual workflows and scheduled tasks |
| Administration | /space/models, /space/governance, /space/teams, /space/settings |
Model catalog, usage metrics, teams, settings |
Connectivity lives in Integrations and Runtimes, where you connect GitHub/GitLab/Cloudflare/Slack, MCP servers, and the desktop/mobile bridge daemon.
Core concepts
Section titled “Core concepts”Conversations and forks
Section titled “Conversations and forks”Every chat is a conversation with a stable id, a provider/model pair, an optional workspace reference (repository), and a fork tree. When you branch from a message, the platform creates a fork: a new conversation whose parentId points at the source, sharing the same rootId. The fork copies all messages up to the branch point. This gives you a Git-like tree of conversation variants you can compare.
Agents and orchestration
Section titled “Agents and orchestration”The chat is not a single prompt loop. A Lead Orchestrator agent can delegate subtasks to specialized agents (engineering, security, data, marketing…), each with its own role, system prompt and recommended tools. Orchestration runs are visible in the ops panel, with per-step status, token usage and cost.
Local-first persistence
Section titled “Local-first persistence”Session state follows a local-first hybrid:
- The heavy data — messages, code, diffs — lives in your browser’s IndexedDB (via the local chat store) and, when the desktop bridge is paired, in the bridge’s local SQLite.
- Only a light index (~200 B per conversation) is stored server-side in Postgres (Supabase) so your sidebar syncs across devices.
This is what makes the platform fast offline and private by default: your conversation content never has to leave your device.
BYOK vault
Section titled “BYOK vault”API keys are stored in an encrypted vault in localStorage (synthhires-credentials), encrypted with AES-256-GCM using a key derived from a device salt (and optionally hardened with a server-side secret). For each request, the client builds a single-use handoff envelope (E2EE-wrapped key + expiry), so the server can proxy the request without ever seeing the plaintext key.
Where to go next
Section titled “Where to go next”- Chat & orchestration — how conversations, streaming and agent delegation work.
- Agents, skills & prompts — the catalog and how to compose your own.
- Models & API keys — providers, the catalog and BYOK.
- Security & BYOK — the exact encryption flow and trust boundaries.