Mere now has a real trifecta.
mere.business
is the cloud workspace for people and durable shared data.
merekit is the agent-native command plane — an open-source
toolkit that bundles 15 app CLIs under a single
mere command, includes
Dynasite for website diagnostics and static bundle publishing,
@merekit/link for declared work graphs,
serves tools to agents over MCP, and stays read-only by default.
mere.run
is the local AI and data runtime. Same workspace, both directions.
Human UI, customer workspaces, approvals, invites, handoffs, and durable shared state.
open business ↗Typed app adapters, JSON contracts, manifests, Link policies, and MCP tools for agents.
install cli ↓Local models, files, media, indexes, generated outputs, and runtime capability checks.
open runtime ↗mere ships
all 15 bundled adapters, honors env overrides, and falls back to app binaries
on PATH when operators need an escape hatch.
Workspace creation, setup, status, handoff, and workspace-aware site operations.
Finance automation gated by per-tenant scoped profiles. Tokens, not browsers.
Website diagnostics, CMS, media, revisions, publishing, and static bundles.
Projects, contacts, knowledge, proposals, and source workflows.
Agent foundations, runtime sessions, generated tools, and share links.
Scheduling, booking, calendar, and time — across tenants and rooms.
Stores, products, orders, Stripe, and checkout — operate the storefront.
Rooms, meetings, agents, diagnostics, recordings, transcripts.
Calls, SMS, conversations, numbers, routing, deployments, diagnostics.
Mailboxes, threads, sending, providers, domains, and drafts.
Donation tenants, campaigns, receipts, Stripe, widgets, settings.
Work apps, releases, shares, capabilities, and publishing flows.
Local media stores, imports, transcription, embeddings, and search.
Password-gated delivery packages, Same Page payloads, and share URLs.
Declared work graphs for projects, role surfaces, operator policy, and Executor-backed tools.
Create, select, inspect, set up, and hand off customer workspaces through the same CLI a human or agent uses every day. No special agency role is required for the Jesse-style operator path.
# workspace lifecycle
mere business workspace create --name "Acme Studio" --slug acme-studio --yes --json
mere business workspace status --workspace ws_123 --json
mere business workspace setup --workspace ws_123 --json
Import an existing website, create a net-new Business site request, or upload a static HTML/CSS/JS bundle generated by Claude, Codex, or another tool. Static bundles stay client-side; Mere controls the runtime.
# existing site, generated site, or static bundle
mere business site import-existing --workspace ws_123 --url https://example.com --json
mere business site create --workspace ws_123 --business-name "Acme Studio" --json
mere business site bundle upload --workspace ws_123 --site-id site_123 --source-dir ./site-dist --json
mere business site bundle publish --workspace ws_123 --site-id site_123 --bundle-id sb_123 --environment live --yes --json
mere dynasite ... to inspect
a site created through Business, edit CMS/media, list or revert revisions,
publish live, and roll static bundles forward or back.
mere-link CLI and the bundled
mere link adapter inside the root command plane.
Link keeps project context in a readable mere.link.yaml: entities, projects, role surfaces, explicit links, operator identity, and the policy that decides which context or writes an operator can use.
# install the source package
npm install -g @merekit/link
# create and validate a work graph
mere-link config init --output mere.link.yaml
mere-link config validate --config mere.link.yaml --json
mere-link context inspect workspace workspace --role work --json
The public @merekit/cli package bundles a generated Link adapter, so agents can stay inside one root command while Link remains the source package for graph behavior, docs, and safety policy.
# same behavior through the root command plane
mere link generate workspace --workspace ws_123 --output mere.link.yaml --yes
mere link policy evaluate workspace workspace --capability project.context.export --operator approved-agent --json
mere link sync projects --config mere.link.yaml --json
mere link executor tools search "monday item" --json
--apply for writes.
Validate YAML, list surfaces, and export one project context without touching external systems.
Dry-run Mere Projects records and URL links from the graph before any write path opens.
Writes require declared Link policy, operator capability checks, and explicit apply flags.
mere setup mere-run resolves an existing binary,
builds from source, or installs a verified DMG. It keeps the runtime setup
owned by the public CLI instead of burying it inside one app adapter.
# prepare mere.run for app use
mere setup mere-run --json
Apps can declare the local models they require. Media currently asks for Parakeet ASR and Qwen3 embeddings so transcripts and searchable segments are ready before local processing.
# pull Media-requested local models
mere setup mere-run models --app media --json
# then process locally
mere media process ./interview.m4a --transcribe --embed
mere.business is where people work. Pixels and pointers, dashboards and detail views, customer records and approvals. It is the durable side of the bridge.
# open the human surface
open https://mere.business
merekit
is agent-native by design — open-source, Apache 2.0. The
mere binary exposes manifest-declared commands as
MCP tools. Read tools are always on. Writes require
--allow-writes. mere.run
supplies the local runtime when the work should happen on the machine.
# scaffold an agent kit for codex / claude
mere agent bootstrap --target codex
# expose to your agent runtime over MCP
mere mcp serve
# write tools, opted-in only
mere mcp serve --allow-writes
# prepare local AI runtime
mere setup mere-run --json
Finance uses per-tenant scoped profiles. Tokens, not sessions; one product, one blast radius.
The root never injects --yes or --confirm. Destructive flags belong to the product.
Only flags a target manifest declares are forwarded. Use apps manifest --app APP --json to see the contract.
# npm npm install -g @merekit/cli # or pnpm pnpm add -g @merekit/cli # requires node ≥ 24 < 26
# agent first run mere agent bootstrap --target codex \ --workspace ws_123 --json # operator first run mere apps list --json mere ops doctor --json mere ops workspace-snapshot --json mere help agent
# runtime and model setup mere setup mere-run --json mere setup mere-run models \ --app media --json # local processing mere media process ./meeting.m4a \ --transcribe --embed