00 · Connectors & CLI

What you install, what you connect, what you run.

Pilot teams self-install the Slack and GitHub apps, drop one CLI command into their agent harness, and start shipping packets. This page lists the public surfaces — what you actually connect and run after we activate your workspace.

01 · CLI

One command for every agent.

# install once, globally
npm install -g @aideps/cli

# bind the agent token we email you with the install link (non-interactive)
aideps init <your-token>

# drop a Work Packet into the repo as the first file the agent reads
aideps packet pull PKT-3F2A1

The CLI lands as @aideps/cli on npm and works in any shell — Mac, Linux, Windows. Same command in every agent harness. No per-agent prompt engineering. Source available on request to pilot teams.

02 · Connectors

Self-install, least-privilege, revocable.

NameStatusWhat it does
SlackshippingRight-click any thread → Create Aideps Packet. Pulls the thread + referenced links into the packet source field.
GitHubshippingWatches PRs from aideps/PKT-* branches. Posts Packet Validation checks per acceptance criterion. Gates risky paths until a human approves.

03 · Agents

Same packet, every agent.

Aideps doesn’t replace your agent — it gives the agents you already use the company-shaped context they’re missing. One packet shape, every harness.

AgentHow it consumes a packet
Claude CodeCLI agent. The packet file is the first thing it reads.
CursorIDE agent. Drop the packet into the repo, point Cursor at it.
Codex / Codex CloudCloud agent. Pulls the packet at session start.
DevinCloud agent. Same packet shape, no per-agent prompting.
Gemini CLICLI agent. Reads the packet from the canonical path.
Custom harnessAny agent that can run a shell command — point it at npx @aideps/cli packet pull.

Want access to the CLI & install links?

The package & install URLs go to pilot teams via team@aideps.dev after we approve your workspace. Async setup, 24h response.

Start Pilot →How it works