20a4a8da87
* docs(readme): rebuild the README around a product hook and job-based features (MUL-5812) The README had drifted badly: 1771 commits landed in three months while its feature list last changed on 2026-05-24, and both screenshots dated to 2026-04-14 — a UI that predates the type-scale migration, the execution log rebuild, and the issue detail rework. Whole surfaces were missing (Chat, Inbox, Projects, usage analytics, self-hosted Git, the chat-bot integrations), the desktop app appeared nowhere at all, and iOS was a footnote under Development. The roster drift had a mechanism: the runtime list was repeated five times per README, so every new provider needed ten hand edits. Four had gone missing (deveco, grok, qwen, qwenpaw). Each README now lists it once, between markers, and scripts/check-readme-runtimes.sh fails CI when either table drifts from scripts/agent-cli-command-names.txt. Structure follows what warp, block/buzz, openclaw, and hermes-agent do: the product screenshot lands before any prose, features are grouped under job verbs rather than flattened into one list (Notion's features page), and the docs table is goal-oriented. Screenshots are the ones already shipping on the docs site, so they are days old rather than months. Moves the Multics origin story out of position two into VISION.md alongside the vision narrative approved in MUL-4877, which had no home in the repo before. Adds a Works today inventory that names the rough edges (iOS not on the App Store, no Android, DingTalk community-maintained) instead of leaving readers to find them. README.zh-CN.md stays a 1:1 mirror and follows the Chinese glossary in apps/docs/content/docs/developers/conventions.zh.mdx: agent as 智能体, issue as 任务, autopilot as 自动化. Co-authored-by: multica-agent <github@multica.ai> * docs(readme): fix nav paths, switch to .zh.md i18n naming, rework project status (MUL-5812) Review feedback on #6506: - The setup steps sent people to Settings for both Runtimes and Agents. Both are sidebar destinations (packages/views/layout/app-sidebar.tsx: runtimes under Configure, agents under Workspace), and the button reads "New agent". - Renames README.zh-CN.md / VISION.zh-CN.md to README.zh.md / VISION.zh.md so translations match the locale suffix the docs site already uses (.zh, .ja, .ko). check-readme-runtimes.sh now discovers README.md plus README.*.md instead of hardcoding the list, so a new locale is covered the day it lands. - Reworks "Works today", which re-listed the features the four groups had just covered and buried the honest part underneath. It is now "Project status": a per-surface table saying how finished each one is, including the parts we'd rather people hear from us (iOS off-store, no Android, DingTalk without an SLA). No feature re-listing. - Drops the banner. It was generic scenery that said nothing about the product and pushed the logo, tagline, and board screenshot below the first viewport. The board screenshot is the hook, so it now leads. Also revises the Chinese throughout. The first pass tracked the English clause by clause and read like a translation; this one keeps the meaning but uses Chinese sentence rhythm, and follows the shipped UI strings — assignee 负责人, in_review 审核中, execution log 执行日志. Co-authored-by: multica-agent <github@multica.ai> * docs(readme): regroup features around the team arc, drop project status (MUL-5812) Co-authored-by: multica-agent <github@multica.ai> * docs(readme): drop the unsuitable inline screenshots from the feature sections (MUL-5812) Co-authored-by: multica-agent <github@multica.ai> * docs(readme): make quick start cloud/desktop-first, keep CLI for self-hosting (MUL-5812) Co-authored-by: multica-agent <github@multica.ai> * docs(readme): smooth out stiff Chinese phrasing across README.zh and VISION.zh (MUL-5812) Co-authored-by: multica-agent <github@multica.ai> * docs(readme): apply translation review — glossary terms, OS metaphor, VISION naturalization (MUL-5812) Co-authored-by: multica-agent <github@multica.ai> * chore(ci): drop the readme-runtimes check (MUL-5812) Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: Lambda <lambda@multica.ai> Co-authored-by: multica-agent <github@multica.ai>
4.5 KiB
Why "Multica"
Multica — Multiplexed Information and Computing Agent.
The name is a nod to Multics, the pioneering operating system of the 1960s that introduced time-sharing — letting multiple users share a single machine as if each had it to themselves. Unix was born as a deliberate simplification of Multics: one user, one task, one elegant philosophy.
We think the same inflection is happening again. For decades, software teams have been single-threaded — one engineer, one task, one context switch at a time. AI agents change that equation. Multica brings time-sharing back, but for an era where the "users" multiplexing the system are both humans and autonomous agents.
In Multica, agents are first-class teammates. They get assigned issues, report progress, raise blockers, and ship code — just like their human colleagues. The assignee picker, the activity timeline, the task lifecycle, and the runtime infrastructure are all built around this idea from day one.
Like Multics before it, the bet is on multiplexing: a small team shouldn't feel small. With the right system, two engineers and a fleet of agents can move like twenty.
The vision, made concrete
Today, adding an AI agent often adds another inbox to manage.
Its work lives in a chat, a terminal, or a private session. Context stays in one person's head. Decisions disappear into threads. When the work moves to another person or agent, the team has to explain it all again.
The promise of AI is not a larger collection of tools. It is a more capable team.
In the future Multica is building, work can begin wherever people already are: a customer conversation, a Slack thread, or a few rough sentences describing what should change. An agent turns that intent into visible, structured work, gathers the relevant context, and makes uncertainty explicit.
If the task is clear, agents can move it forward. If it changes product behaviour, introduces risk, or depends on a trade-off, the right person is brought in before the work continues. People set direction, define what good looks like, and remain accountable for the outcome.
Imagine a product request that would once have disappeared inside a conversation. In Multica, it becomes a shared plan. Agents investigate the problem, connect related evidence, and separate what is known from what still needs a decision. Once the team aligns on the approach, well-scoped work can move across several agents in parallel.
The team does not review status theatre. It reviews the work itself: the plan, the document, the implementation, the diff, the preview, the test result, and the unresolved questions. People can redirect the work, raise the quality bar, approve the next stage, or stop it. Agents keep the routine coordination moving without hiding what they are doing or why.
When the work is complete, its history does not vanish with the session. The original intent, the decisions made, the actions taken, the artifacts produced, and the final outcome remain connected. The next agent does not start from zero. A new teammate can understand not only what happened, but why.
The same model applies wherever knowledge work moves through context, collaboration, and review. Agents can organise research, prepare customer briefs, draft content, progress support work, or coordinate client deliverables. Humans spend less time carrying information between tools and chasing handoffs. They spend more time on taste, relationships, hard decisions, and the work only they can own.
Multica is not an autonomous company running beyond human control. It is the shared operating system for people and agents doing consequential work together.
People set direction and remain accountable. Agents keep the work moving. Multica preserves the team's shared understanding and turns it into coordinated action.
That is what it means to make humans and AI agents work as one team — and to become the system of record and action for human-agent work.
Where we are on that path
This document describes the future Multica is building, not a feature list. For what actually works today, see the README — everything listed there is live, and each feature links to its docs.