agentchannel@3.66.0
CAUTION· startup onlyPublisher claims: "Hand work between your team's agents (Claude Code, Codex) and follow it in one panel: the ach CLI, MCP server and runner for AgentChannel v2" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
ACH_AUTH_EXIT_CODEACH_CF_SECRETACH_RUN_TOKENKIRO_API_KEYor--cf-token/--cf-secretConfiguration, not credentials: ACH_AGENT, ACH_CF_ID, ACH_CHANNEL, ACH_CODEX_BIN, ACH_CODEX_THREAD_ID, ACH_DEBUG, ACH_HANDOFF_VERSION, ACH_HUB, ACH_KEY, ACH_KEYSTORE, ACH_KIRO_BIN, ACH_NO_TRACE, ACH_NOTIFIER, ACH_PUBLIC_URL, ACH_RUN_STREAM, ACH_SERVICE_DIR, ACH_SERVICE_PLATFORM, ACH_SESSION_NOTICES, ACH_SUPERVISED, ACH_TASK_ID, ACH_THREAD_ID, AGENTCHANNEL_HOME, CLAUDE_CONFIG_DIR, CODEX_HOME, CODEX_SESSION_ID, CODEX_THREAD_ID, DISPLAY, INVOCATION_ID, LC_ALL, LC_MESSAGES, WAYLAND_DISPLAY, XPC_SERVICE_NAME- Where it talks to
- no vendor host named in the codeAlso reelanything.com, kiro.dev, apple.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names reelanything.com, kiro.dev, apple.com as well as its own vendor. The guard injects ACH_AUTH_EXIT_CODE, ACH_CF_SECRET, ACH_RUN_TOKEN, KIRO_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 3.49.0
vet-skills diff agentchannel 3.49.0 3.66.0This version reaches for something 3.49.0 did not: 1 new host (reelanything.com). Compared from the two recorded runs, not from source.
- New hosts
- reelanything.com
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-22 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Privileged sudo command; Privileged sudo command; Privileged sudo command. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 46 s · 2 scenarios · 0 deviationsStatic findings
...(linger ? [] : ['Note: it stops when you log out of this machine. To keep it running: sudo loginctl enable-linger "$USER"']),Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.export declare const LINGER_CMD = "sudo loginctl enable-linger \"$USER\"";Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* the password); with no terminal (an agent ran the join line) only say it: sudo would wait for a password nobody can type.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** A shell line with this terminal's stdin/stdout/stderr (sudo asks for its password there); its exit code. */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return s.env.AGENTCHANNEL_HOME || achHome({ ...env, AGENTCHANNEL_HOME: '' });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.export const LINGER_CMD = 'sudo loginctl enable-linger "$USER"';Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.jenv = { ...env, AGENTCHANNEL_HOME: agentHome(me.name, env) };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./** A file whose contents are secrets by convention (.env, .npmrc, key files): its content is never put in a trace. */Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// ACH_AUTO_UPDATE=0 turns the installing off (the log and the session notice remain).Fix: Pin versions and sources; vendor anything fetched at install time.return shim || dev ? { ...env, PATH: path } : env;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const { ACH_SUPERVISED: _, ...env } = process.env;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.let jenv = ownHome ? { ...env, AGENTCHANNEL_HOME: ownHome } : env;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// no terminal to type a sudo password in (an agent ran the line): say it, run nothingFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** Runs a shell line with this terminal (sudo can ask for a password); the exit code. Absent: sandbox fixes are only printed. */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// nothing to run (no safe command for this machine), or no terminal to run sudo in: say what to do and go onFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* commands that fix it (sudo included), run only after Enter in a terminal;Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* then stops with it and nobody notices until tasks pile up (2026-11-10). In a terminal: ask, then run it there (sudo asks forFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** A file whose contents are secrets by convention (.env, .npmrc, key files): its content is never put in a trace. */Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./** A shell line with this terminal's stdin/stdout/stderr (sudo asks for its password there); its exit code. */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.const INSTALL = 'curl -fsSL https://cli.kiro.dev/install | bash';Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return { ...env, ...extra };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…retFile(path) { const base = path.split(/[\\/]/).pop() ?? ''; return /^\.env(\..*)?$/i.test(base) || /^\.(npmrc|netrc|pypirc)$/i.test(base) || /^id_(rsa|ed2…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const menv = sess.how === 'dir' ? { ...env, AGENTCHANNEL_HOME: sess.home } : env;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./** `npx -y @koalaauto/agentchannel@<spec>`: how messages and MCP entries start the CLI without relying on PATH. */Fix: Pin versions and sources; vendor anything fetched at install time.…eclared on the runner's machine: MCP servers, commands and skills (`capabilities.json`, README). The agent's page lists them under Tools. Missing one: ask its owner. |\n| Invite people, create or move channels, budgets | Admin work (`ach a…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…e path meanwhile.`, 'machine', `remove it or put this CLI first on PATH (or use npx -y ${npmSpec()} …); see below`); add('fix', 'info', shadowFix(first, a…Fix: Pin versions and sources; vendor anything fetched at install time.* with npx or `node dist/src/cli.js`). Returns the dir to prepend to PATH.Fix: Pin versions and sources; vendor anything fetched at install time.* "Unable to locate Codex CLI binaries". npx installs every ach that starts with the same spec into one cache directory and, on aFix: Pin versions and sources; vendor anything fetched at install time.* npx cache (`.../_npx/...`) or in a node_modules/.bin (e.g. npx puts thisFix: Pin versions and sources; vendor anything fetched at install time.export declare function sessionDeliverer(server: McpServer, env?: NodeJS.ProcessEnv, exec?: Exec): (text: string) => Promise<boolean>;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them./** The one line a teammate pastes: npx fetches the CLI and `join` sets everything up. */Fix: Pin versions and sources; vendor anything fetched at install time.return spec ? { ok: true, why: `through npx (${spec})` } : { ok: false, why: `npx does not start ${PKG_NAME}` };Fix: Pin versions and sources; vendor anything fetched at install time.* with npx or `node dist/src/cli.js`). Returns the dir to prepend to PATH.Fix: Pin versions and sources; vendor anything fetched at install time.out(v.json ? r : `note posted (message ${r?.message?.id ?? '?'})`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why./** `npx -y @koalaauto/agentchannel@<spec>`: how messages and MCP entries start the CLI without relying on PATH. */Fix: Pin versions and sources; vendor anything fetched at install time.* "Unable to locate Codex CLI binaries". npx installs every ach that starts with the same spec into one cache directory and, on aFix: Pin versions and sources; vendor anything fetched at install time.// started by a service that starts through the npx cache: make it start the install in the AgentChannel homeFix: Pin versions and sources; vendor anything fetched at install time.out(v.json ? m : `${p.cmd} posted`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.if (starts || /^[A-Za-z][A-Za-z ]*:\s+npx /.test(line))Fix: Pin versions and sources; vendor anything fetched at install time./** The node_modules dir an npx cache run of this CLI lives in, or undefined when it is not one. */Fix: Pin versions and sources; vendor anything fetched at install time.* PATH while `npx agentchannel` runs).Fix: Pin versions and sources; vendor anything fetched at install time.export const JOIN_LINE_RE = /^npx -y @koalaauto\/agentchannel@\S+ join (ach2\.\S+)$/;Fix: Pin versions and sources; vendor anything fetched at install time.Setup: npx -y @koalaauto/agentchannel@3 join <ach2.invite> [--name <n>] [--service] [--yes] [--dry-run] (run it in theFix: Pin versions and sources; vendor anything fetched at install time.// and the start fails with ETARGET; and every `@3` process shares one npx cache dir that the next release is written over).Fix: Pin versions and sources; vendor anything fetched at install time.const INSTALL = 'curl -fsSL https://cli.kiro.dev/install | bash';Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.// not the npx cache's bin dirs: they vanish when npm clears the cache, and hold bundled tools (a codex) that are not the user'sFix: Pin versions and sources; vendor anything fetched at install time.add('hub', cfg.hub ? 'ok' : 'fail', cfg.hub ? `${cfg.hub}${env.ACH_HUB ? ' (ACH_HUB)' : ''}` : 'no hub configured', 'hub', `paste the join line from your admin (npx -y ${npmSpec()} join ach2....)`);Fix: Pin versions and sources; vendor anything fetched at install time./** The one line a teammate pastes: npx fetches the CLI and `join` sets everything up. */Fix: Pin versions and sources; vendor anything fetched at install time.return { dir, problem: `${dir} stays mode ${after ? mode(after.mode) : '?'} after chmod 0700: this /tmp does not keep modes` };Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.// npx at start-up (npx re-resolves `@3` on every start: in the minutes after a release npm names a version it does not serve yet,Fix: Pin versions and sources; vendor anything fetched at install time.* Started from npx (`npx -y <spec> mcp`): some time after start, copy this release into the install in the AgentChannel home and pointFix: Pin versions and sources; vendor anything fetched at install time.* From the npx cache the unit runs `npx -y <spec>` (the cache may be cleared;Fix: Pin versions and sources; vendor anything fetched at install time.the join line npx -y @koalaauto/agentchannel@3 join <blob>. Language: --lang, else the hub's (Memory) language.Fix: Pin versions and sources; vendor anything fetched at install time.* Put the release this CLI is into the install by copying its npx cache dir (nothing is downloaded, so nothing waits on npm), and pointFix: Pin versions and sources; vendor anything fetched at install time.export const JOIN_HINT = 'They paste the line in a terminal (Node 20+); npx fetches the CLI. To type `ach` yourself: `npm i -g ' + PKG_NAME + '`. ' +Fix: Pin versions and sources; vendor anything fetched at install time.const word = (w) => new RegExp(`(?:ach|npx -y @koalaauto/agentchannel@3|\\|)\\s+${w.replace(/[-/\\^$*+?.()|[\]{}]/g, '\\$&')}(?![\\w-])`);Fix: Pin versions and sources; vendor anything fetched at install time.return `npx -y ${npmSpec(version)} join ${blob}`;Fix: Pin versions and sources; vendor anything fetched at install time.// a codex that npx put on PATH (this package's SDK dependency) is not the user's CodexFix: Pin versions and sources; vendor anything fetched at install time.out(v.json ? r : `posted ${r.id} in #${r.channel_name ?? hit?.name ?? channelRef(name)}${r.url ? `: ${absUrl(env, r.url)}` : ''}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// `npx -y <spec>` re-resolves the spec at every start, which fails while npm catches up with a release. At start the runnerFix: Pin versions and sources; vendor anything fetched at install time.* the npx `ach` entries at it (mcpmove.ts), so the next session starts without npm. A runner service does the same on Mac and Linux;Fix: Pin versions and sources; vendor anything fetched at install time.* the spec at every start (and fails while npm catches up with a release). `node-cache`: starts node on a file inside the npx cache,Fix: Pin versions and sources; vendor anything fetched at install time.// in the AgentChannel home (appinstall.ts). npx re-resolves the spec at every session start and fails while npm catches up with aFix: Pin versions and sources; vendor anything fetched at install time.// release ("Reconnect ach"). Two callers: a runner of the install (its service was just moved there), and `ach mcp` started from npxFix: Pin versions and sources; vendor anything fetched at install time.* entry, never a path in the npx cache.Fix: Pin versions and sources; vendor anything fetched at install time.// a home install already here (appinstall.ts): the restart may start its launcher instead of npx (the service was moved to it, orFix: Pin versions and sources; vendor anything fetched at install time.* This agent's own service (ownService), when it starts through the npx cache: rewritten to start `command`, the install in theFix: Pin versions and sources; vendor anything fetched at install time.// run through npx (the join line): this release is copied into the AgentChannel home and the MCP entry and service start itFix: Pin versions and sources; vendor anything fetched at install time.// started from the npx cache), and exits with UPDATE_EXIT_CODE.Fix: Pin versions and sources; vendor anything fetched at install time.// - A service that starts through the npx cache: node on a cached file (early releases) never moves to a newer release, andFix: Pin versions and sources; vendor anything fetched at install time.… `client_too_old` | Your `ach` is older than the hub accepts | Your owner runs `npm install -g @koalaauto/agentchannel@latest`. |\n| `forbidden` / `not_found` | Not yours, or not visible to you (private ch…Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed./** User-installed claude / codex (never the bins npx puts on PATH). */Fix: Pin versions and sources; vendor anything fetched at install time.// own dir of the install in the AgentChannel home, appinstall.ts; or a global install) or relies on npx to fetch it (a serviceFix: Pin versions and sources; vendor anything fetched at install time.// from there (appinstall.ts); npx at every start fails while npm catches up with a release. The npx spec if the copy failed;Fix: Pin versions and sources; vendor anything fetched at install time.* Points the npx `ach` entries at `achCmd`, keeping their scope and AGENTCHANNEL_HOME. `exec` runs in the project dir, where Claude CodeFix: Pin versions and sources; vendor anything fetched at install time.const npx = runFromNpx(self);Fix: Pin versions and sources; vendor anything fetched at install time.const npx = (x) => !!x && /(^|[\\/])npx(\.cmd)?$/i.test(x);Fix: Pin versions and sources; vendor anything fetched at install time.…turn (o.version ?? VERSION).includes('-') ? { kind: 'other', why: 'started with npx from an exact prerelease version: run the join line (or `ach run --install-service`)…Fix: Pin versions and sources; vendor anything fetched at install time./** Install the release. npx needs nothing now (the restart fetches it). A global install is `npm install -g`, scripts off, then read back. */Fix: Pin versions and sources; vendor anything fetched at install time./** `app`: node on the launcher of the install in the AgentChannel home (appinstall.ts). `npx`: starts `npx -y <spec>`, which re-resolvesFix: Pin versions and sources; vendor anything fetched at install time.// Moving the `ach` MCP entries that start npx (`npx -y @koalaauto/agentchannel@3 mcp`, on Windows also `cmd /c npx ...`) to the installFix: Pin versions and sources; vendor anything fetched at install time.…hen the runner it started (its command line holds the same --dir) const kill = (like) => `Get-CimInstance Win32_Process | Where-Object { $_.CommandLine -like…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** Does this service start through the npx cache (`npx -y <spec>`, or node on a cached file)? */Fix: Pin versions and sources; vendor anything fetched at install time.* Run through npx, the helper runs the same pinned npx spec as the MCPFix: Pin versions and sources; vendor anything fetched at install time./** What starts the CLI: node + the launcher of the install in the AgentChannel home, node + cli.js of another install, or `npx -y <spec>`. */Fix: Pin versions and sources; vendor anything fetched at install time./** True when this CLI runs from the npx cache (it disappears; install it first). */Fix: Pin versions and sources; vendor anything fetched at install time./** True when this CLI runs from the npx cache (it disappears; install it first). */Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @koalaauto/agentchannel@3.66.0 as of 1 h ago. This is the package itself, not its dependencies.
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Unclaimed publisher≈ +8 on the totalClaim koalaauto: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.