View source

V0.1.0 · MIT · SELF-HOSTED

Your AI agents. One operating system.

A self-hosted workspace for persistent agents, people, schedules, tasks, files, documents, and durable runs.

Explore on GitHub Read the docs

THE PRODUCT

One workspace. Every agent surface.

SYNTHETIC DEMO DATA · NO LIVE WORKSPACE CONTENT
Synthetic ReplicantOS channel with persisted Replicant replies and a workspace roster.
Channels and durable agent continuity
Synthetic Harness settings with Codex, Claude Agent SDK, OpenCode, and Grok Build.
Four harness adapters
Synthetic Runs view with history, durable output, events, usage, and an approval.
Inspectable run control
Synthetic schedule list with assigned Replicants, timing, and Run Now controls.
Scheduled work
Synthetic safe-root file browser and UTF-8 source editor.
Safe files and documents
Enter the system
01

THE SYSTEM

AGENTS NEED MORE THAN A CHAT WINDOW

Give intelligence
a place to live.

A model can answer a prompt. A Replicant keeps bounded channel continuity, works from its separate directory, and returns on schedule.

ReplicantOS turns scattered terminal sessions into one legible operating layer—for people and agents working together over time.

01CHAT + CHANNELS
02TASKS + SCHEDULES
03FILES + DOCUMENTS
04RUNS + POLICY
02

FOUR ADAPTERS

BRING THE AGENT RUNTIME YOU TRUST

One control plane.
Four ways to think.

The production server registers four adapters behind one durable run lifecycle. Adapter sessions, output, tools, approval requests, usage, and failures are normalized internally. Authenticated approval decisions, authorized cancellation, and on-demand doctor results are implemented in v0.1.0; each provider still requires its supported host runtime and provider-native authentication.

H/01
CX

Codex

Stable adapter for a host-installed Codex app server, with normalized events, tools, and approval requests.

  • THREAD CONTINUITY
  • APPROVAL EVENTS
H/02
CL

Claude Agent SDK

Stable adapter for the optional, separately installed SDK, with explicit settings and permission callbacks.

  • SESSION RESUME
  • PERMISSION HOOKS
H/03
OC

OpenCode

Beta adapter for host-installed OpenCode ACP sessions exposed through the same lifecycle.

  • LOCAL TRANSPORT
  • CAPABILITY AWARE
H/04
GB

Grok Build

Beta adapter for host-installed Grok Build ACP sessions, with normalized progress, usage, and failure states.

  • STREAMED ACTIVITY
  • HOST TOOL REQUIRED
NORMALIZED CONTRACT

START

STREAM

APPROVE

RESUME

INSPECT

DIRECTORY MAP / SYNTHETICREPLICANT / ARCHIVIST
SEPARATE ROOTSBOUND CHANNELSESSION RESUMED

03 / PERSISTENT

Sessions end.
The work does not.

Each Replicant has a persona plus separate workspace and memory directories. Channel-triggered runs can resume the provider session; memory remains an explicit host directory, not a hidden global brain.

  • 01SEPARATE REPLICANT WORKSPACES
  • 02BOUND CHANNEL CONTINUITY
  • 03SEPARATE MEMORY DIRECTORIES
  • 04PROVIDER SESSION CONTINUITY

04 / SCHEDULES

Automation
with receipts.

Assign a Replicant to timezone-aware cron, trigger it with Run Now, and preserve retry attempts in basic durable history.

  • 01TIMEZONE-AWARE CRON
  • 02RUN NOW + RETRY
  • 03DURABLE BASIC HISTORY
  • 04BOUND REPLICANT
SCHEDULE / WEEKDAY BRIEFACTIVE
09:15AMMON—FRI / LOCAL TIME
NEXT RUNMON 03 AUG / 09:15
  1. 02 AUG 09:15complete / attempt 142.8s
  2. 01 AUG 09:15complete / attempt 139.4s
  3. 31 JUL 09:15complete / retry 158.2s
$ RUN NOW ↵
05

TEAM

ONE WORKSPACE, CLEAR BOUNDARIES

Collaborative
by design.

Human owners, admins, and members share a system without inheriting each other’s access. Scoped allow and deny grants follow the resource, not the screen someone happens to open.

CAPABILITYOWNERADMINMEMBERUNGRANTED
CHANNELSALLALLGRANTEDDENIED
REPLICANTSALLALLGRANTEDDENIED
FILE MUTATIONPOLICYPOLICYEXPLICITDENIED
DATABASE VIEWERPOLICYPOLICY—DENIED
01

Channels that carry context

Authorized messages persist, enqueue bound Replicants, resume continuity, and store the final reply.

02

Replicants with explicit reach

View and interact grants are evaluated before a run starts or an event broadcasts.

03

Authenticated run controls

Approval decisions, run cancellation, and on-demand provider diagnostics are wired through authorized server routes and the live UI.

06

INSPECTABILITY

POWER YOU CAN ACCOUNT FOR

Nothing important
hides behind “working.”

All feature panels below use synthetic data.

RUN HISTORYSYNTHETIC
AR
INDEX DOCUMENTSCODEX / COMPLETE
OP
VERIFY RELEASECLAUDE / RETRY 1

Queued, running, complete, failed, and retry attempts leave basic durable history.

FILESSAFE ROOT
  • ⌄workspace/
  • ⌄release/
  • MDreadiness.md 18 KB
  • JSverify.mjs 6 KB
  • ›research/

Realpath containment and symlink escape rejection keep browsing inside approved roots.

DOCUMENT LIBRARYSYNTHETIC
⌕ Filter approved text metadata⌘K

Filter approved Markdown and text metadata, then open a hash-verified raw preview without indexing hidden host data.

DATABASE VIEWERREAD ONLY
TABLE runs · ALLOWLIST · LIMIT 50
STATUSSTARTED_AT
COMPLETE09:40:04
RUNNING09:40:31
QUEUED09:41:00

Admin-only table allowlists, protected-column masking, row limits, bounded pages, and no arbitrary SQL.

07

SECURITY

YOUR HOST. YOUR CREDENTIALS. YOUR POLICY.

Power tools stay
behind the boundary.

ReplicantOS is designed for a dedicated, non-root host account. Product authorization is enforced server-side; the operating system remains the outer execution boundary.

SECURITY DEFAULTSPOLICY / V0.1
01

TELEMETRY

DISABLED
02

PROVIDER CREDENTIALS

HOST-NATIVE
03

FILE EDITING

SAFE ROOT / UTF-8
04

DATABASE VIEW

MASKED / READ-ONLY
05

SESSIONS

OPAQUE / REVOCABLE
06

AUDIT TRAIL

APPEND-ONLY
>

principle: explicit access over ambient trust

AUTH / 01

Authorize at the source

HTTP, channel, file, task, schedule, run, and database operations all resolve an actor and policy on the server.

FILES / 02

Contain real paths

Approved roots are enforced after canonical resolution, including explicit rejection of symlink escapes.

CREDS / 03

Keep native credentials native

Harnesses use their own host login. The v0.1 baseline does not persist provider credentials in ReplicantOS.

08

INSTALL

FREE / MIT / SELF-HOSTED

Run it where your
agents already work.

SUPPORTED SOURCE PATH

ReplicantOS runs on your host, next to the local harnesses and files you choose to approve. This website never hosts a workspace or agent session.

SOURCE BUILD / V0.1.0 NODE 22+ · PNPM 10.32.1 
git clone --branch v0.1.0 --depth 1 https://github.com/replicantos/replicantos.git
cd replicantos
corepack enable
pnpm install --frozen-lockfile
cp .env.example .env
pnpm build
pnpm run doctor
pnpm start

These commands install the supported v0.1.0 source tag. Review the operator guide before exposing an installation beyond its host.

01 / LOCAL

Loopback by default

Open 127.0.0.1:8787 locally. Plain HTTP exposure beyond the host is rejected.

02 / NETWORK

HTTPS at the edge

Keep the app on loopback and use one exact public HTTPS origin through a same-host reverse proxy.

03 / IDENTITY

No default account

The first browser visit creates the owner. No seeded login or provider credential ships with the project.

Installation guide Review the source

THE CONTROL PLANE IS OPEN

Your agents are ready
for an operating system.

Install the tagged public release, read the architecture, and help shape a durable home for self-hosted agents.

View v0.1.0 Read the docs

V0.1.0 IS PUBLIC UNDER MIT. WORKSPACES AND AGENT SESSIONS REMAIN ON OPERATOR-CONTROLLED INFRASTRUCTURE.