FridayOS

Mission Control for serious AI agent work.

One premium control plane for Hermes, Claude Code, Codex, Perplexity, providers, MCP tools, workspaces, review queues, approvals, runtime history and live operational signals.

Control rooms4+Hermes, Codex, Claude Code, Perplexity and more
Runtime surfaces20+agents, providers, reviews, jobs, ledgers and artifacts
Refresh loop8snear-realtime cockpit polling with stale/error handling
Safety posturegatedworkspace policy, write policy, firewall and approval layers
Hermes
Codex
Claude Code
Perplexity
LIVEFridayOSpolicy · routing · ledger
Agent network
01
Mission Control

Live snapshot and command cockpit

02
Hermes

Research, orchestration and planning

03
Claude Code

Refactor, code review and implementation

04
</>
Codex

CLI coding worker and verification loops

05
Perplexity

Fresh source research and citation support

06
MCP

Filesystem, Context7 and tool contracts

07
Review Queue

Approval gates for sensitive actions

08
Ledger

Replayable runtime records

Control-plane flow
flow

Observe

See every agent, provider, workspace and status in one cockpit.

flow

Route

Use workspace policy to decide which agent and provider should handle the job.

flow

Review

Hold sensitive provider connections, writes and external effects behind approval gates.

flow

Replay

Use ledger history and activity records to understand what happened and why.

How FridayOS operates
01

Observe

Snapshot the agents, providers, runtime stores, workspace map and readiness checks.

02

Decide

Apply identity, workspace, provider, firewall and write-policy rules before work starts.

03

Execute

Route the job to the right agent/provider pair while preserving approval and budget constraints.

04

Prove

Persist activity, usage, artifacts, review decisions and ledger entries for replayable execution.

Capability matrix

Built for agent teams that need control, not just chat.

FridayOS turns agents, tools, providers and approvals into a visible operating system. Every surface should explain what is allowed, what is blocked, where work is routed and what happened afterwards.

Identity + status

Agent command

Give every agent a role, permission tier, provider route and operational state instead of treating agents like loose chat windows.

Latency + policy

Provider routing

Route work across OpenAI, Anthropic, Gemini, Perplexity, local models and future providers with fallback and budget rules.

Allowlist + purpose

Workspace boundaries

Separate Thea, WorldMind, Rendetalje, Renos and FridayOS tasks so tools, memory and context stay scoped.

Approve + block

Review gates

Hold external effects, production impact and sensitive writes behind explicit review decisions before execution.

Trace + replay

Runtime ledger

Record jobs, artifacts, reviews, activity, usage and black-box audit events so execution becomes explainable.

Tools + contracts

MCP surface

Prepare a real operating layer for MCP tools, filesystem access, Context7, Sequential Thinking and future adapters.

Real workspaces
Ship the operating layer

Make every agent action observable, gated and replayable.

Start in Mission Control, inspect the live snapshot, then move into providers, jobs, reviews, ledgers and artifacts.

Landing narrative
01

Hero: Mission Control for every AI agent

Designed for premium exploration, implemented as production Next.js control-plane surfaces.

02

Problem: too many agents, no shared control plane

Designed for premium exploration, implemented as production Next.js control-plane surfaces.

03

Solution: agents, providers, tools, workspaces and reviews in one OS

Designed for premium exploration, implemented as production Next.js control-plane surfaces.

04

Proof: ledger, policies, adapter model and MCP registry

Designed for premium exploration, implemented as production Next.js control-plane surfaces.

05

Use cases: TekUp, Thea, WorldMind, Rendetalje and Renos

Designed for premium exploration, implemented as production Next.js control-plane surfaces.

06

CTA: open Mission Control

Designed for premium exploration, implemented as production Next.js control-plane surfaces.