The operating system for Organizational Agents.

Anyone can build an agent. JoyStream lets teams build or bring them, earn trust through evidence, and operate them together in production.

Non-technical users create in plain language, while the organization gets the operating system underneath: lifecycle, authority, credentials, observability, Runs, collaboration, and control.

The Agent Engineering Divide

Building an agent is easy. Production is engineering.

People across Marketing, Sales, HR, Finance, IT, and Engineering can now describe the work they want done in plain language. But production agents require more than prompting—they need the software system underneath: ownership, lifecycle, credentials, approvals, observability, Runs, and operational control.

What users experience
Build in chatBring a Skill, Agent, or PluginBuild with the CLI
The agent engineering divide
What JoyStream provides
Capability SpecsRecipesDry RunsPilotsProgressive AuthorityRuns / Semantic TicketsVault / CredentialsControl PlaneHuman + Agent Workspaces

JoyStream separates what users see from what the organization needs.

Describe the work, and what emerges is a structured Organizational Agent—with lifecycle, evidence, and operational control—without asking the person who described it to assemble the engineering stack by hand.

Make

Describe the work. JoyStream builds the system underneath.

Create an agent from recurring work, or bring an existing Agent, Skill, or Agent Plugin. Define the work, connect tools, Dry Run the behavior, inspect the evidence, and move toward production—while JoyStream turns your description into a versioned Spec and a predictable Recipe.

The JoyStream chat: a work owner asks for an agent that summarizes a GitHub project — open, closed, and done issues — and posts it to Slack. Joyvis confirms the skills (github-project-ticket-summary, slack-post-message), flags that GitHub isn't connected yet, and drafts a GitHub Project Summary → Slack plan to approve.
Operate

When a team depends on it, run it like production software.

JoyStream manages the full lifecycle—lifecycle state, production Runs, semantic tickets, failures, approvals, intervention, performance, and evolution over time. Make and Operate are one switch, one lifecycle.

JoyStream in Make mode — the build prompt, the Spine (Draft → Capability Spec → Dry Run → Pilot → Live), the Draft Agents table, and the Parlor (Skills, MCP Connectors).
Progressive Agent Authority

Agents earn authority through evidence.

An Organizational Agent earns its authority—it doesn’t jump from prototype to production on confidence alone. Dry Runs establish intended behavior. Pilot provides bounded evidence. Live authority increases when the organization has enough evidence to trust it.

Draft
Capability Spec
Dry Run
Pilot
Live
Dry Run
Pilot
Live
Dry Run
See what the agent will do—without affecting production.
systems: simulated · live calls: 0
Pilot
Let it operate with bounded authority, and observe the results.
systems: real · scope: bounded
Live
Expand responsibility once the evidence supports it.
authority: approved on evidence
The Evidence screen: readiness (Build complete, two connections missing, Conform coming soon), the Dry Run / Pilot / Live evidence rows with run counts and pass results, and the promote decision — Run a dry run, Promote to Pilot, Promote to Live.
More evidence. More trust. More authority.
Runs & Semantic Tickets

Every run becomes accountable organizational work.

Each execution turns into a semantic ticket your team can read: what the agent attempted, what completed, what failed or blocked, which tools it used, and where a human needs to step in.

Dry Run shows what an agent intends to do. Runs show what it actually did.

The Runs view — every agent execution as an inspectable record: status (Completed / Failed / Rejected), agent, run id, progress, mode (Dry Run / Live), version, and when it started.
Every run is a semantic ticket—status, mode, version, and progress at a glance.
The Runs board — agent executions grouped by state so the team can see work in motion across Dry Run, Pilot, and Live.
Work in motion, grouped by state.
A failed Run — the step that blocked, the tool it was calling, and the error, so a human knows exactly where attention is required.
When a run fails, the ticket shows exactly where—and why.
Collaborate

Built, operated, and owned by teams—not individuals.

Organizational Agents live in shared Human + Agent Workspaces. Teams own them together, approve what moves to production, and keep visibility into the work agents perform across the organization.

Human + Agent Workspace — where a team and its agents share the work
A Human + Agent Workspace hub — the team's agents, their lifecycle stages, and recent Runs in one shared place.
Shared ownership — members, roles, and the agents they operate together
A workspace's members and roles — the people who own and operate the team's Organizational Agents together.
Agent Universe

Working agents. Adopt one, or contribute your own.

Bring the Skills, Agent Plugins, and Agents you already use, share them across your organization, and adopt what other teams have built—every one through the same trusted lifecycle. This is where reuse becomes real.

Control Plane

Give agents access. Keep the organization in control.

One control plane for the connections, credentials, authority, and tool activity your agents depend on. Agents get permission to act. The organization keeps the credentials, the scope, and the record.

From zero to first agent in an hour

Anyone can build an agent. JoyStream makes it organizational.

Start from recurring work, an existing Agent, Skill, or Agent Plugin, and get the operating system that makes it trustworthy, operational, and reusable in production.