\n\n---\n\nAblo is coordination infrastructure for agents, applications, services, and\npeople working on shared state.\n\nEvery write goes through it, so authority, idempotency, conflicts, ordering,\nand confirmation are enforced in one place. Your Postgres remains the source of\ntruth.\n\nGroups structure which shared state reaches each person or agent. Declare the\ndata's scope and participant authority, then let authorized subscriptions keep\nreactive views current; HTTP agents explicitly read or observe changes. Start\nwith [Groups and shared context](./docs/groups.md) to connect membership, access,\nloading and updates.\n\n## Why Ablo\n\nSoftware used to have one writer: a human clicking through an application. AI\napplications now have humans, agents, workflows, and services acting\nconcurrently. Databases keep transactions consistent. They do not coordinate\nautonomous work that reads now, reasons for thirty seconds, and writes later.\n\nHumans handle this naturally. We see that somebody is editing, agree on who\ntakes which part, wait our turn, and look again before continuing. Ablo gives\nsoftware actors those same capabilities: bounded authority, shared ownership,\nfresh context, safe handoffs, and an attributed record of what happened.\n\n## Start\n\n```sh\nnpm install @abloatai/ablo\nnpx ablo init\nnpx ablo dev\n```\n\n`ablo dev` prepares an isolated Ablo branch for your Git branch, writes its\ntemporary credential to gitignored `.env.local`, pushes the schema, and watches\nfor changes.\n\nRead and write through one typed API:\n\n```ts\nconst order = await ablo.orders.read({ id: orderId });\n\nif (!order) throw new Error('Order not found');\nawait ablo.orders.update({\n id: order.id,\n data: { status: 'approved' },\n reads: [order],\n});\n```\n\n`confirmed` means the authoritative database reported the change back. The\nsame commit can be retried safely if the caller loses its connection.\n\nWhen work takes thirty seconds instead of one request, coordinate before the\nagent starts reasoning:\n\n```ts\nawait using claim = await ablo.orders.claim({ id: orderId });\n\nconst priced = await pricingAgent(claim.data);\n\nawait ablo.orders.update({\n id: claim.data.id,\n data: { total: priced.total, status: 'repriced' },\n claim,\n});\n```\n\nAnother actor touching the same work waits fairly and receives fresh state when\nits turn begins. If the agent fails, the claim releases automatically. If its\ncontext became stale, the write is rejected instead of silently overwriting\nwork it never saw.\n\nIf you use AI SDK, expose the same operation as a typed model tool:\n\n```ts\nimport { updateTool } from '@abloatai/ablo/ai-sdk';\n\nconst approveOrder = updateTool(ablo.orders, {\n description: 'Approve an order after reviewing it.',\n inputSchema: z.object({ orderId: z.string() }),\n id: ({ orderId }) => orderId,\n apply: () => ({ status: 'approved' }),\n});\n```\n\nAblo supplies `readTool`, `createTool`, `updateTool`, and `deleteTool` over the\nsame authoritative resources. AI SDK keeps ownership of the model loop and tool\nexecution.\n\nFor a model call that needs several reads plus application-owned retrieval or\nmemory, [`context()`](./docs/context.md) awaits the selected values and carries\nthe exact Ablo rows into the write's `reads` option. It does not add search,\nmemory, or a model runtime.\n\nUse `@abloatai/ablo` for agents and backend code,\n`@abloatai/ablo/client` for live applications, and\n`@abloatai/ablo/react` for React. All entrypoints share the same schema,\nauthority, commits, claims, and ordered changes.\n\nRead the [Quickstart](https://docs.abloatai.com/quickstart), browse\n[docs.abloatai.com](https://docs.abloatai.com), or run `npx ablo docs`.\n\n## Navigating the source\n\nThis repository preserves the package ownership boundaries instead of\nflattening the implementation into `packages/ablo`:\n\n- `packages/ablo` is the branded public facade. Its files mostly re-export the\n package that owns each API.\n- `packages/transaction` owns the shared model-operation contracts and the\n headless HTTP/WebSocket transport implementation.\n- `packages/humans` owns the reactive WebSocket/local/React implementation.\n\nThat means searching only inside `packages/ablo/src` will not find the\nimplementation of `create`, `update`, `delete`, or `claim`. Read the\n**[source code map](./CODEMAP.md)** for a verb-by-verb ownership table and\nguided call traces for both the default and reactive clients.\n\n## Contributing\n\nAblo is free and open source. You can help by\n[opening an issue](https://github.com/Abloatai/ablo/issues),\n[suggesting a feature](https://github.com/Abloatai/ablo/issues/new), or\n[contributing code](https://github.com/Abloatai/ablo/pulls).\n\nPlease report vulnerabilities privately through\n[GitHub Security Advisories](https://github.com/Abloatai/ablo/security/advisories/new).\n\n## License\n\nApache License 2.0. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).\n","readmeFilename":"README.md"}
![\"Ablo\"](\"assets/banner.png\")
\n![\"npm\"](\"https://img.shields.io/npm/v/@abloatai/ablo?style=flat-square&color=2563eb\")
![\"license\"](\"https://img.shields.io/badge/license-Apache--2.0-2563eb?style=flat-square\"){kind=icon}
![\"node](\"https://img.shields.io/badge/node-%E2%89%A524-22c55e?style=flat-square\"){kind=icon}
![\"types](\"https://img.shields.io/badge/types-included-2563eb?style=flat-square\"){kind=icon}