Install the driver

The driver is a service that manages the digital objects themselves. Installing it puts three binaries under ~/.dobj/bin/:

What	Where
`dobjd` — driver daemon (REST/SSE on `:7717`, MCP on `:7718`)	`~/.dobj/bin/`
`dobj` — terminal CLI	`~/.dobj/bin/`
`dobj-mcp-proxy` — stdio bridge for agents that only speak stdio (e.g. Claude Desktop)	`~/.dobj/bin/`

The driver installs with an empty action catalog — applications ship separately as plugins (.pexe files). The steps below install the binaries, start the daemon, and add an example plugin such as craft-basics or craft-rocket.

Release binaries are baked with the hosted synchronizer and relayer endpoints, so a fresh install needs no configuration.

Let an agent install it

Paste this prompt into any MCP-aware agent (Claude Code, Cursor, ...):

Read https://raw.githubusercontent.com/dobjlabs/digital-objects-network/main/INSTALL.md, install and start the Digital Objects driver, install the craft-rocket plugin, and configure MCP for this agent if supported.

The guide walks the agent through every step below and includes instructions for plugin install and MCP connection. Setup takes a couple of minutes.

Install by hand

Install the binaries

Downloads the latest release into ~/.dobj/bin and prints a PATH hint. To pin a version, set DOBJ_VERSION (bash) / $env:DOBJ_VERSION (PowerShell) to a release tag first.

curl -fsSL https://raw.githubusercontent.com/dobjlabs/digital-objects-network/main/install.sh | sh

irm https://raw.githubusercontent.com/dobjlabs/digital-objects-network/main/install.ps1 | iex

Start the daemon

~/.dobj/bin/dobj start

& "$env:USERPROFILE\.dobj\bin\dobj.exe" start

Install example applications

dobj install takes a local .pexe path or an http(s) URL, validates it, and hot-reloads the running daemon's catalog — no restart needed.

Two examples ship with each release:

craft-basics — a small crafting demo.
craft-rocket — a larger factory tech tree.

Install either example, or run both commands to load both.

# Starter demo:
~/.dobj/bin/dobj install https://github.com/dobjlabs/digital-objects-network/releases/latest/download/craft-basics.pexe
 
# Larger factory demo:
~/.dobj/bin/dobj install https://github.com/dobjlabs/digital-objects-network/releases/latest/download/craft-rocket.pexe

# Starter demo:
& "$env:USERPROFILE\.dobj\bin\dobj.exe" install https://github.com/dobjlabs/digital-objects-network/releases/latest/download/craft-basics.pexe
 
# Larger factory demo:
& "$env:USERPROFILE\.dobj\bin\dobj.exe" install https://github.com/dobjlabs/digital-objects-network/releases/latest/download/craft-rocket.pexe

Verify

~/.dobj/bin/dobj status      # pid + HTTP healthcheck
~/.dobj/bin/dobj actions     # installed plugin actions
~/.dobj/bin/dobj state-root  # 64-hex root: the hosted synchronizer is reachable

& "$env:USERPROFILE\.dobj\bin\dobj.exe" status
& "$env:USERPROFILE\.dobj\bin\dobj.exe" actions
& "$env:USERPROFILE\.dobj\bin\dobj.exe" state-root

Connect a client

Every client talks to the same daemon:

CLI — ~/.dobj/bin/dobj (add ~/.dobj/bin to your PATH)
Claude Code / MCP agents — claude mcp add --transport http dobj http://127.0.0.1:7718/mcp
Stdio-only agents (e.g. Claude Desktop) — point them at ~/.dobj/bin/dobj-mcp-proxy

Manual install

Prefer to fetch the archives yourself? Detect your platform's target triple, then download the two tarballs from the releases page (the dobjd tarball bundles dobj-mcp-proxy):

case "$(uname -s)-$(uname -m)" in
  Darwin-arm64)   TARGET=aarch64-apple-darwin ;;
  Darwin-x86_64)  TARGET=x86_64-apple-darwin ;;
  Linux-x86_64)   TARGET=x86_64-unknown-linux-gnu ;;
  *) echo "unsupported platform: $(uname -sm)"; exit 1 ;;
esac
 
RELEASE=https://github.com/dobjlabs/digital-objects-network/releases/latest/download
mkdir -p ~/.dobj/bin
curl -fsSL "$RELEASE/dobjd-$TARGET.tar.gz" | tar -xz -C ~/.dobj/bin
curl -fsSL "$RELEASE/dobj-$TARGET.tar.gz"  | tar -xz -C ~/.dobj/bin
chmod +x ~/.dobj/bin/dobjd ~/.dobj/bin/dobj ~/.dobj/bin/dobj-mcp-proxy

$TARGET  = "x86_64-pc-windows-msvc"     # the only Windows target built
$RELEASE = "https://github.com/dobjlabs/digital-objects-network/releases/latest/download"
$DOBJ    = "$env:USERPROFILE\.dobj"
New-Item -ItemType Directory -Force -Path "$DOBJ\bin" | Out-Null
foreach ($name in @("dobjd", "dobj")) {
    $tmp = "$DOBJ\$name-$TARGET.tar.gz"
    curl.exe -fsSL "$RELEASE/$name-$TARGET.tar.gz" -o $tmp
    tar -xzf $tmp -C "$DOBJ\bin"
    Remove-Item $tmp
}

Then continue from Start the daemon above.

Point at different infrastructure

The hosted endpoints are defaults, not requirements. See public infrastructure for how to point ~/.dobj/settings.json at any synchronizer / relayer pair — including your own.

Suggest changes to this page