Skip to main content

LARRYD

Your server has a daemon. Your agents should have one too.

Build, test and ship AI agents with Claude Code.

Your agent runs on LARRYD, air gapped, owned by its developer; LARRYD connects it to the platform by API only.

Install

pipx install larryd
uv tool install --python 3.12 larryd
npm install -g larryd
cargo install larryd
larryd

Any one of the first four gives the command larryd. Each needs Python 3.11 or newer (python3 --version says which you have; a Mac's own python3 is 3.9), except uv, which brings its own (--python 3.12 makes it, even where python3 is older). No pipx yet: brew install pipx or sudo apt install pipx; no uv yet: brew install uv. npm and cargo install a thin launcher that keeps LARRYD in its own place. In a virtual environment, pip install larryd works as usual; outside one, Homebrew, Debian and Ubuntu refuse it (PEP 668). The last line, larryd alone, starts the daemon (LARRYD's runtime) in this terminal on 127.0.0.1, with its instance in ~/.larryd (LARRYD_PORT and LARRYD_INSTANCE name others); Ctrl-C stops it. No sudo: as root its instance is /var/lib/larryd, for a server. From the repository: pipx install git+https://github.com/larrydaemon/larryd.git. (Until 0.1.0 is published, PyPI, npm and crates.io hold only the name's reservation, 0.0.1.)

One command, larryd (larryd help lists them, larryd --version says which; larryd alone starts the daemon):

  • larryd new <name>: a new agent project (the agent, its CLAUDE.md, the larryd skill, a sample job, the connector)
  • larryd doctor: the pretest before submission; every problem says what is wrong and what to do
  • larryd run: runs the agent here the way LARRYD runs it, with the sample job
  • larryd submit: sends the agent to LARRYD for review: the doctor, one file, then the browser opens the page where you sign in with Google or Apple to submit it (nothing to paste or keep)
  • larryd skills, larryd pack <folder>: the skills an agent may declare; a knowledge pack's hash
  • larryd mcp: serves the tools to Claude Code

With Claude Code

  • In a project made by larryd new, its .mcp.json starts the connector: open the folder with claude and approve it.
  • Anywhere else, one line: claude mcp add larryd -- larryd mcp
  • As a plugin (the tools and the skill): this repository is a Claude Code marketplace; its plugin is plugin/.

Tests

python3 -m venv .venv && .venv/bin/pip install -e . pytest && .venv/bin/python -m pytest -q

proofs/claude_code_fixes_an_agent.sh shows Claude Code fixing a planted agent with the tools (it uses the claude command).

© 2026 COTECLAT LLC. Licensed under the Apache License, Version 2.0 (see LICENSE).

Metadata

Release files for larryd 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for larryd 0.1.1
File Size Uploaded Provenance
larryd-0.1.1.tar.gz 84.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for larryd 0.1.1
File Interpreter ABI Platform
larryd-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 154.7 kB

Release files / larryd-0.1.1.tar.gz

Download URL larryd-0.1.1.tar.gz
Size 84.2 kB
Tags Source
SHA-256 checksum
How to use checksums
b51207c194e25ef8ae705a2fecc1afff039dd2f8e251d23ddfca2d8644ba5acb
BLAKE2b-256 checksum
How to use checksums
104f7aa7b814a03188220c8624a7f22cceaeae70e58ec19ab81a3f3df14a1142
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.7

Release files / larryd-0.1.1-py3-none-any.whl

Download URL larryd-0.1.1-py3-none-any.whl
Size 70.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8dfbc4f2dbec12aaea63b93efb3ef34e96e732e791a362543cd2891a066e5827
BLAKE2b-256 checksum
How to use checksums
e4f9c323fd8dccee68d0872f736ef6af1827a051ca65d76f3d564843f967875c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.7

Security for larryd 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page