For developers
You’re building an app that runs inside someone else’s Linkworld tenant — a per-tenant container that wakes on demand, exposes tools to the tenant’s agents, and talks to other apps via grants and wires.
Pick a starting point:
New here
Section titled “New here”- Quickstart — scaffold, run locally, deploy to the platform. Five minutes.
- Concepts — the mental model: manifest, scopes, lifecycle, trust boundaries.
- Install the CLI —
pip install linkworld, verify, configure.
Building
Section titled “Building”- Manifest reference — every field your
linkworld.app.yamlcan set. - Python SDK · TypeScript SDK ·
Browser bridge — handler signatures,
the
ctxAPI surface, error types. - lw-ui + components catalog — the CSS framework for in-app UIs.
- CLI reference —
init,dev,eval,chat,mcp.
Collaboration surfaces
Section titled “Collaboration surfaces”- Heartbeats — recurring agent routines with cheap pre-filters.
- Cross-app calls —
ctx.team.delegate(intra-app),ctx.apps.invoke(cross-app),ctx.events.emit(pub/sub). - Group rooms — humans + agents in one shared thread.
- Commitments — due-dated promises that surface in the inbox.
- Tutorial — cross-app lead handoff — two apps, the full collaboration stack end to end.
How-to guides
Section titled “How-to guides”- Capabilities — server-side surfaces, in-app UI, storage, identity, third-party APIs.
- Building app UIs · Right-side panel · Install settings — surfacing your app to the tenant.
- Workflow hooks · Lifecycle hooks · Recurring work — when your code runs.
- Secrets — the vault, dev defaults vs tenant overrides, rotation.
- MCP setup — point Cursor / Claude Code at the platform for in-editor scaffolding and validation.
- Best practices · Troubleshooting · FAQ.
Two SDKs, one contract
Section titled “Two SDKs, one contract”# Pythonpip install linkworldlinkworld init my-app --lang python# TypeScriptnpm install -g @linkworld_ai/clilinkworld init my-app --lang typescriptSame manifest schema, same handler signatures, same ctx API
(ctx.tools, ctx.secrets, ctx.team, ctx.apps, ctx.events,
ctx.rooms, ctx.commitments, ctx.kv). Cross-SDK CI tests assert
they stay in lockstep.
Status
Section titled “Status”The Open App Platform is in alpha. The wire format is stable and the cross-app collaboration stack is live in production, but 0.x SDK APIs may break until the first external partner ships. Pin your SDK version and watch the GitHub releases.