Meridian OS

An open-source company OS for running teams of humans and AI agents from one operational console.

Meridian OS is an operational control plane for companies made of humans and AI agents.

Agent orchestration is not enough to run a company. A company OS needs to know who owns what, which goals matter, what work is blocked, how fast tokens and dollars are burning, what approvals are pending, and what happened after the operator closed the tab.

Meridian brings those surfaces into one live system. The result is less "chat with an agent" and more "talk to the company, inspect its state, and approve the moments that matter."

More operating surfaces:

Work	Approvals	Finance

Meridian ships with a simulation engine that ticks about every 2.6 seconds. While it is running, AI agents send heartbeats, tasks advance, token counts grow, budget lines accrue spend, and the audit log keeps recording activity.

The simulation can be paused from the sidebar. Without any real runtime connected, Meridian still behaves like a live company console, which makes it useful for design, demos, and product development.

Kimi Space is the operator chat surface. It understands OS commands such as:

create task: refresh onboarding emails, assign to Bea, p1
assign HAL-1042 to Ingrid
move HAL-1042 to review
install Context7 on Juno
budget report

When a command resolves, Meridian dispatches a real store action. When no command matches and the local Kimi runtime is ready, Meridian calls the user's local kimi CLI and shows the model reply with a trace.

Requirements:

• Node 20+
• Optional for real local chat: Kimi Code CLI installed at ~/.kimi-code/bin/kimi and logged in with kimi login

Install and run:

npm install
npm run dev

Open the Vite app on port 4173. Build and preview:

npm run build
npm run preview

Meridian has two Kimi integration paths.

Local runtime endpoints:

GET  /local-runtime/status
POST /local-runtime/kimi/chat

Safety properties:

• One local Kimi chat runs at a time.
• Chat messages are capped at 8k characters.
• Calls time out after 180 seconds.
• The bridge uses a dedicated .kimi-runtime workdir.
• Tokens are never returned by any endpoint.

The Kimi Space header shows a local runtime badge when the local CLI path is ready. If the runtime is missing, Meridian keeps working in simulation mode.

OAuth proxy endpoints:

POST /kimi-oauth/device
POST /kimi-oauth/token

The OAuth connection status is persisted in localStorage, but the device code and tokens are not persisted by the client.

src/
  App.tsx                 shell, navigation, company switcher, simulation toggle
  components/             shared primitives, command palette, Kimi connection card
  lib/
    store.tsx             reducer, selectors, simulation engine, localStorage persistence
    types.ts              company, agent, goal, task, approval, activity, Kimi types
    seed.ts               seeded multi-company operating world
    skills.ts             installable skill registry
    kimiAuth.ts           client for the device-flow OAuth proxy
  styles/                 token-driven global CSS and app primitives
  views/                  Command, Kimi Space, Work, Goals, Org, Agents, Skills,
                          Approvals, Finance, Activity, Reports, Portfolio
vite.config.ts            React plugin plus Kimi OAuth proxy and local Kimi bridge

Middleware bridge:

Kimi Space
   |
   | same-origin fetch
   v
Vite middleware
   |---------------------> /kimi-oauth/* -> auth.kimi.com
   |
   | local process spawn
   v
~/.kimi-code/bin/kimi -p
   |
   v
.kimi-runtime workdir + user's stored Kimi credentials

The frontend is React 19 with strict TypeScript, Vite 6, and no runtime dependencies except lucide-react. The visual system is a dark ops-console UI using Geist and Geist Mono, token-driven CSS, shared primitives, one status vocabulary, and mono text for machine values.

Read ARCHITECTURE.md before changing views or shared patterns.

Meridian is local-first. The most sensitive path is the development middleware that can spawn the user's local Kimi CLI; it is designed for user-consented local development, does not expose tokens through API responses, serializes local Kimi chats, caps input size, and uses a dedicated workdir.

See SECURITY.md for the threat model, supported versions, and reporting process.

The first push focuses on hardening the local runtime, persistence, tests, and CI. Next comes a real adapter layer for task execution, more local runtimes, stronger approvals, and a mobile layout pass.

See ROADMAP.md for the Now/Next/Later plan.

Contributions are welcome. Start with CONTRIBUTING.md, keep npm run build green, and include screenshots for UI changes.

Meridian OS is released under the MIT License.