aclade
v1.0.3
Published
Aclade — autonomous AI experts that do real work. `npx aclade` connects your machine to your Aclade team with a zero-trust local connector.
Maintainers
Readme
Aclade
Autonomous AI experts that do real work. Aclade rents you AI employees — a CTO who reviews code, an analyst who pulls data, a marketer who ships campaigns — and they can act on your own machine through a zero-trust local connector.
This package (aclade) is the front door: one command to connect this machine to your Aclade team.
Docs & examples: github.com/aclade-ai-expert/aclade-docs — CLI reference, Python SDK guide, architecture notes, and worked examples.
Quickstart
# 1. Get a connection token: https://aclade.com → Settings → Local Agent
# 2. Connect this machine (installs & daemonizes automatically):
npx aclade connect --token <TOKEN>
# 3. Check it:
npx aclade statusOr install globally:
npm install -g aclade
aclade connect --token <TOKEN>No Node.js on the machine? The portal's one-liner bootstraps a private Node for you (arguments after -- reach the installer, not curl):
curl -fsSL https://aclade.com/install.sh | bash -s -- --token <TOKEN>Commands
| Command | What it does |
|---|---|
| aclade connect --token <T> | Starts (or replaces) the local agent daemon |
| aclade connect --token <T> --workspace /path | Same, but the agent refuses to operate outside /path |
| aclade status | Local agent state + live fleet as seen by aclade.com |
| aclade stop | Stops the local agent |
| aclade --version | Show versions |
Anything else is passed straight through to the aclade-agent connector.
Python
Prefer import aclade? The official Python SDK drives the same platform from code:
import aclade
team = aclade.Aclade(token="<TOKEN>")
for e in team.experts():
print(e["name"], e["title"])
result = team.delegate(team.experts()[0], "Summarize our top 3 customer complaints")
print(result["run"]["report"])Security model
- Zero-trust polling. No inbound ports are opened. The agent polls
aclade.comoutward over HTTPS and nothing else. - Short-lived tokens. The connection token is a signed 12-hour session bound to your workspace. It can never be another tenant's, and it can never carry admin authority. Treat it like a password. The agent rotates it automatically in the final 90 minutes (proof-of-possession), so a running daemon stays connected without operator action.
- Scoped file tools.
--workspace /pathconfines the file tools (read, write, edit, list, glob, grep, index) to one directory. Be aware thatexecute_bashandschedule_cronare NOT confined by that scope — they run on your machine, which is the point of the connector. - The AI stays in the cloud. This package contains no LLM logic, weights, or reasoning loops. All intelligence runs on Aclade infrastructure; the agent is a thin, inspectable executor that does exactly what the platform instructs — and nothing it does not.
- Set-and-forget. The agent self-updates through npm. Under a supervisor, start it with
--foregroundso the supervisor owns restarts (see the aclade-agent README); on servers, pm2 is the usual choice.
What runs where
┌─────────────────────────────┐ HTTPS polling (outbound only) ┌──────────────────────────────┐
│ Your machine │ ◄─────────────────────────────────────────► │ aclade.com │
│ │ tasks / results, 12h signed token │ │
│ aclade-agent (this pkg) │ │ The harness: 409 roles × │
│ executes: bash, files, │ │ personas, tools, RAG, │
│ grep, browser, embeddings │ │ metering — all server-side │
└─────────────────────────────┘ └──────────────────────────────┘Troubleshooting
- Logs:
~/.aclade-agent.log - Config:
~/.aclade-agent.json(contains your token — it's written0600for a reason) - Token expired? Issue a fresh one in the portal and re-run
aclade connect --token <TOKEN>— the new daemon replaces the old one automatically.
Copyright © Aclade. Proprietary software (UNLICENSED), distributed exclusively for users of the Aclade platform. aclade.com
