Chaperone v0.1.4

Chaperone 0.1.4 — filesystem coordination for concurrent Claude agent sessions
against a shared fileserver.

Install

Coordinator — one per site, on-prem beside the fileserver. Note throughout that
addr (where the socket binds) and public_url (what a laptop connects to) are
different settings.

Windows: download chapr-coord-0.1.4-windows-x86_64.msi and run it. It places the
binary, registers and starts the service, and opens the port. For a fleet:

msiexec /i chapr-coord-0.1.4-windows-x86_64.msi COORD_SHARE=\\FS01\Sales COORD_URL=http://FS01:8787 /qn

A silent install prints nothing, so the values every laptop needs are written to
handover.txt in the data directory; chapr-coord handover reprints them. The
coordinator configures itself on its first start, and never touches a coord.toml that
already exists — so an upgrade keeps your settings.

Linux: download chapr-coord-0.1.4-linux-x86_64 and run it with no arguments. The
executable is the installer: a bare invocation runs the setup wizard, and serve
takes over once a coord.toml exists.

macOS: there is no coordinator build, deliberately. A Mac fronting a shared fileserver
is a deployment nobody runs and nothing tests, and an artifact whose only claim is that
it compiled is worse than an absent one. The macOS endpoint is unaffected.

Endpoint — one per user machine. Two forms, same binary.

Claude Desktop: download chaperone-endpoint-0.1.4-<os>.mcpb and double-click it
(Settings → Extensions). It asks for the coordinator URL and the coordinated location;
identity comes from the OS logon, so there is nothing else to set.

Any other MCP host: download the bare chapr-endpoint-0.1.4-<os> binary. The
endpoint is a standard MCP server over stdio configured entirely by environment
variables, so anything speaking MCP can drive it — .mcpb is Claude Desktop's install
format, not a requirement. The binary prints its own registration:

chapr-endpoint print-config claude-code   # a `claude mcp add …` one-liner
chapr-endpoint print-config generic       # the portable mcpServers JSON block

The config goes to stdout alone, so print-config generic > .mcp.json is a usable file.
Set CHAPR_COORD_URL and CHAPR_ROOT first and it prints your real values instead of
placeholders.

Verify

sha256sum -c SHA256SUMS      # or: Get-FileHash on Windows

Worth knowing

• Nothing here is code-signed — the MSI included. Windows will show a SmartScreen
  prompt on the installer, and an administrator has to choose to continue past it. That
  is a deliberate open decision, not an oversight. The .mcpb bundles cannot be signed
  even in principle: signing is broken upstream in the mcpb CLI (node-forge: "PKCS#7
  signature verification not yet implemented"), so Claude Desktop reports every bundle as
  unsigned regardless. Accountability rests on the audit trail; managed fleets can
  pre-approve both via Intune/GPO. Verify what you downloaded with SHA256SUMS.
• Windows binaries link the CRT statically, so no Visual C++ redistributable is
  needed — the trade is that CRT security fixes arrive with a Chaperone rebuild rather
  than via Windows Update.
• macOS is exercised on the POSIX path only. CI runs the unit suite and the
  end-to-end job (coordinator + smoke suites + self-test) on macOS, so these artifacts
  are no longer build-only. But POSIX uses advisory flock: nothing covers a Mac
  driving an SMB share. Invariant 3 — the mandatory lock the write path rests on — is
  proven on Windows against a real SMB share, and nowhere else.
• Only Claude Desktop and Claude Code have been driven end to end. The endpoint is a
  standard MCP server, so other hosts should work, and print-config generic emits the
  portable form — but "should" is not "does", and we do not test them.
• The coordinator's OS and the endpoints' OS are independent. A Linux coordinator with
  Windows endpoints, or the reverse, is an ordinary deployment.
• Every artifact carries LICENSE and NOTICE; the .mcpb bundles carry them inside.

Built by GitHub Actions from the v0.1.4 tag.

Chaperone v0.1.3

Chaperone 0.1.3 — filesystem coordination for concurrent Claude agent sessions
against a shared fileserver.

Install

Coordinator — one per site, on-prem beside the fileserver.

Download chapr-coord-0.1.3-windows-x86_64.exe (or the Linux build) and run it
with no arguments. The executable is the installer: a bare invocation runs the setup
wizard, and serve takes over once a coord.toml exists. Note that addr (where
the socket binds) and public_url (what a laptop connects to) are different settings.

Endpoint — one per user machine. Two forms, same binary.

Claude Desktop: download chaperone-endpoint-0.1.3-<os>.mcpb and double-click it
(Settings → Extensions). It asks for the coordinator URL and the coordinated location;
identity comes from the OS logon, so there is nothing else to set.

Any other MCP host: download the bare chapr-endpoint-0.1.3-<os> binary. The
endpoint is a standard MCP server over stdio configured entirely by environment
variables, so anything speaking MCP can drive it — .mcpb is Claude Desktop's install
format, not a requirement. The binary prints its own registration:

chapr-endpoint print-config claude-code   # a `claude mcp add …` one-liner
chapr-endpoint print-config generic       # the portable mcpServers JSON block

The config goes to stdout alone, so print-config generic > .mcp.json is a usable file.
Set CHAPR_COORD_URL and CHAPR_ROOT first and it prints your real values instead of
placeholders.

Verify

sha256sum -c SHA256SUMS      # or: Get-FileHash on Windows

Worth knowing

• The .mcpb bundles are unsigned. Signing is broken upstream in the mcpb CLI
  (node-forge: "PKCS#7 signature verification not yet implemented"), so Claude Desktop
  reports every bundle as unsigned regardless. Accountability rests on the audit trail;
  managed fleets can pre-approve the bundle via Intune/GPO.
• Windows binaries link the CRT statically, so no Visual C++ redistributable is
  needed — the trade is that CRT security fixes arrive with a Chaperone rebuild rather
  than via Windows Update.
• macOS is exercised on the POSIX path only. CI runs the unit suite and the
  end-to-end job (coordinator + smoke suites + self-test) on macOS, so these artifacts
  are no longer build-only. But POSIX uses advisory flock: nothing covers a Mac
  driving an SMB share. Invariant 3 — the mandatory lock the write path rests on — is
  proven on Windows against a real SMB share, and nowhere else.
• Only Claude Desktop and Claude Code have been driven end to end. The endpoint is a
  standard MCP server, so other hosts should work, and print-config generic emits the
  portable form — but "should" is not "does", and we do not test them.
• The coordinator's OS and the endpoints' OS are independent. A Linux coordinator with
  Windows endpoints, or the reverse, is an ordinary deployment.
• Every artifact carries LICENSE and NOTICE; the .mcpb bundles carry them inside.

Built by GitHub Actions from the v0.1.3 tag.

Chaperone v0.1.2

Chaperone 0.1.2 — filesystem coordination for concurrent Claude agent sessions
against a shared fileserver.

Install

Coordinator — one per site, on-prem beside the fileserver.

Download chapr-coord-0.1.2-windows-x86_64.exe (or the Linux build) and run it
with no arguments. The executable is the installer: a bare invocation runs the setup
wizard, and serve takes over once a coord.toml exists. Note that addr (where
the socket binds) and public_url (what a laptop connects to) are different settings.

Endpoint — one per user machine. Two forms, same binary.

Claude Desktop: download chaperone-endpoint-0.1.2-<os>.mcpb and double-click it
(Settings → Extensions). It asks for the coordinator URL and the coordinated location;
identity comes from the OS logon, so there is nothing else to set.

Any other MCP host: download the bare chapr-endpoint-0.1.2-<os> binary. The
endpoint is a standard MCP server over stdio configured entirely by environment
variables, so anything speaking MCP can drive it — .mcpb is Claude Desktop's install
format, not a requirement. The binary prints its own registration:

chapr-endpoint print-config claude-code   # a `claude mcp add …` one-liner
chapr-endpoint print-config generic       # the portable mcpServers JSON block

The config goes to stdout alone, so print-config generic > .mcp.json is a usable file.
Set CHAPR_COORD_URL and CHAPR_ROOT first and it prints your real values instead of
placeholders.

Verify

sha256sum -c SHA256SUMS      # or: Get-FileHash on Windows

Worth knowing

• The .mcpb bundles are unsigned. Signing is broken upstream in the mcpb CLI
  (node-forge: "PKCS#7 signature verification not yet implemented"), so Claude Desktop
  reports every bundle as unsigned regardless. Accountability rests on the audit trail;
  managed fleets can pre-approve the bundle via Intune/GPO.
• Windows binaries link the CRT statically, so no Visual C++ redistributable is
  needed — the trade is that CRT security fixes arrive with a Chaperone rebuild rather
  than via Windows Update.
• macOS is exercised on the POSIX path only. CI runs the unit suite and the
  end-to-end job (coordinator + smoke suites + self-test) on macOS, so these artifacts
  are no longer build-only. But POSIX uses advisory flock: nothing covers a Mac
  driving an SMB share. Invariant 3 — the mandatory lock the write path rests on — is
  proven on Windows against a real SMB share, and nowhere else.
• Only Claude Desktop and Claude Code have been driven end to end. The endpoint is a
  standard MCP server, so other hosts should work, and print-config generic emits the
  portable form — but "should" is not "does", and we do not test them.
• The coordinator's OS and the endpoints' OS are independent. A Linux coordinator with
  Windows endpoints, or the reverse, is an ordinary deployment.
• Every artifact carries LICENSE and NOTICE; the .mcpb bundles carry them inside.

Built by GitHub Actions from the v0.1.2 tag.

Chaperone v0.1.1

Chaperone 0.1.1 — filesystem coordination for concurrent Claude agent sessions
against a shared fileserver.

Install

Coordinator — one per site, on-prem beside the fileserver.

Download chapr-coord-0.1.1-windows-x86_64.exe (or the Linux build) and run it
with no arguments. The executable is the installer: a bare invocation runs the setup
wizard, and serve takes over once a coord.toml exists. Note that addr (where
the socket binds) and public_url (what a laptop connects to) are different settings.

Endpoint — one per user machine. Two forms, same binary.

Claude Desktop: download chaperone-endpoint-0.1.1-<os>.mcpb and double-click it
(Settings → Extensions). It asks for the coordinator URL and the coordinated location;
identity comes from the OS logon, so there is nothing else to set.

Any other MCP host: download the bare chapr-endpoint-0.1.1-<os> binary. The
endpoint is a standard MCP server over stdio configured entirely by environment
variables, so anything speaking MCP can drive it — .mcpb is Claude Desktop's install
format, not a requirement. The binary prints its own registration:

chapr-endpoint print-config claude-code   # a `claude mcp add …` one-liner
chapr-endpoint print-config generic       # the portable mcpServers JSON block

The config goes to stdout alone, so print-config generic > .mcp.json is a usable file.
Set CHAPR_COORD_URL and CHAPR_ROOT first and it prints your real values instead of
placeholders.

Verify

sha256sum -c SHA256SUMS      # or: Get-FileHash on Windows

Worth knowing

• The .mcpb bundles are unsigned. Signing is broken upstream in the mcpb CLI
  (node-forge: "PKCS#7 signature verification not yet implemented"), so Claude Desktop
  reports every bundle as unsigned regardless. Accountability rests on the audit trail;
  managed fleets can pre-approve the bundle via Intune/GPO.
• Windows binaries link the CRT statically, so no Visual C++ redistributable is
  needed — the trade is that CRT security fixes arrive with a Chaperone rebuild rather
  than via Windows Update.
• The macOS artifacts are built, not exercised. Nothing in the endpoint is
  Linux-specific, so macOS takes the same POSIX path Linux does and compiles cleanly —
  but no one has run it there. Treat it as untested rather than supported.
• Only Claude Desktop and Claude Code have been driven end to end. The endpoint is a
  standard MCP server, so other hosts should work, and print-config generic emits the
  portable form — but "should" is not "does", and we do not test them.
• The coordinator's OS and the endpoints' OS are independent. A Linux coordinator with
  Windows endpoints, or the reverse, is an ordinary deployment.
• Every artifact carries LICENSE and NOTICE; the .mcpb bundles carry them inside.

Built by GitHub Actions from the v0.1.1 tag.

Binary release v0.1.0

Full Changelog: https://github.com/Korsdal/Chaperone/commits/v0.1.0