> ## Documentation Index
> Fetch the complete documentation index at: https://docs.drkm.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Build on the global mesh.

> One interface for intelligence, distributed compute, and the systems around you.

## One interface. Every target.

An **outpost** is an installation of Darkmatter on a machine you choose: a laptop, a rack, a vehicle, a cloud tenancy. It runs an agent, serves models, joins the services around it and takes work from its peers. Talk to it in the console or the terminal, describe bulk work in Python, and give the agent your tools and procedures. Outposts enrolled in one mesh find each other and share eligible work.

## Choose your starting point

> [card] [Install the CLI](https://docs.drkm.dev/installation.md)
>
> One command on an Apple silicon Mac or on x86-64 or ARM64 Linux, then start an outpost or sign in to one.

> [card] [Run your first workload](https://docs.drkm.dev/quickstart.md)
>
> Talk to the agent, submit a Python worker, collect the rows.

> [card] [Add devices to the mesh](https://docs.drkm.dev/mesh.md)
>
> Invite a second machine with a single-use code and place work across both.

> [card] [Connect your tools](https://docs.drkm.dev/connectors.md)
>
> Give the agent your services, MCP servers and skill files.

## The core concepts

| Concept | What it is |
| - | - |
| **Outpost** | An installation of the platform, on its own or enrolled in a mesh. It runs the agent and the console, serves models, exposes tools and contributes compute, whatever the hardware. |
| **Mesh** | A private network of outposts. The outpost that created it, the *authority*, admits the others with single-use invitations. An outpost belongs to one mesh at a time, and only members of one mesh run each other’s work. |
| **Job** | Durable work with its own identity: sealed inputs and code, partitions placed on eligible outposts, retries, and a settled result with explicit coverage. It outlives the script or conversation that started it. |
| **Connection** | An outside service the outpost joins as a client so the agent can use its tools: a built-in integration or any MCP server. |
| **Skill** | A saved procedure the agent follows: a name, a description of when it applies, and Markdown instructions. Shipped with the platform or written by you. |
| **Model** | A hosted provider or a model the outpost serves on its own hardware. Chat, agents and jobs pick from one catalog, and *Auto* picks a reachable one for each call, here or on a peer. Each reply says which. |

The console’s sidebar is Chat, Schedules, Outposts and Overwatch, and Watchdog once a video connection is configured; Settings opens from your account menu. Administrators manage the mesh, connections, models, keys, people and updates under Settings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.