Local observability for Claude Code and Codex. Sessions, subagents, tokens, model costs, and delivery evidence in one console.
# Add to your Claude Code skills
git clone https://github.com/LockedinLabs-AI/agent-consoleGuides for using ai agents skills like agent-console.
See how agent-console compares with popular alternatives.
agent-console is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by LockedinLabs-AI. Local observability for Claude Code and Codex. Sessions, subagents, tokens, model costs, and delivery evidence in one console. It has 212 GitHub stars.
agent-console's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/LockedinLabs-AI/agent-console" and add it to your Claude Code skills directory (see the Installation section above).
agent-console is primarily written in JavaScript. It is open-source under LockedinLabs-AI on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agent-console against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Captured from --demo. Every figure in it is generated and stamped DEMO.
The same screen in the light theme.
Get started · Documentation · Architecture · Security · Contribute · Changelog
Installing with Claude Code or Codex? Give it this repository's URL and ask it to follow INSTALL.md. The same guide works if you prefer to install it yourself: choose the current source, an npm archive, or a standalone download, then verify the version and open the console.
This page describes v0.4.0, published as the
v0.4.0 release
and as the source on main. Run from source to use the current console:
git clone https://github.com/LockedinLabs-AI/agent-console.git
cd agent-console
node bin/agent-console.mjs --open
You need Git and Node.js 22 or newer, or use Download ZIP
instead of Git. There is no account to create, no package install and no build
step. The command runs this checkout, reads the Claude Code and Codex history already on
this computer, and opens the console in your browser, signed in, normally at
http://127.0.0.1:6787. To look around first without reading anything of
yours, add --demo before --open.
In the first thirty seconds you see: the last 24 hours of tokens (or the last hour, 7 days or 30 days), split into cache read, cache write, output and uncached input; their list-price estimate; burn right now, in tokens per minute and dollars per hour; one lane per session with its model, its subagents and its last hour of activity; and every machine and person reporting, each with a share of the total.
Nothing leaves a machine but counts. Only model ids, minute timestamps,
token counts and salted hashes, and never a prompt, a reply, a file path or a
file's contents. A test pushes transcripts full of planted canaries through
the real reporter and the real hub and checks every byte that crosses the wire.
The console itself sends nothing anywhere: no telemetry, no update check, no
account. (Three opt-ins, each off unless you pass it: --share-project-names
sends each project folder's name, never its path; --share-alerts and
--share-tool-activity send alerts and tool calls as kinds and counts.)
The installation guide covers all three routes and what to do after closing the console. Downloads live in GitHub Releases. There is no separate desktop installer or hosted dashboard to sign up for; the executable starts the console in your browser.
Choose a version as well as an installation method:
| Channel | Current availability |
|---|---|
| Source on main | v0.4.0 source. Use Node.js 22+ and the commands above, or Download ZIP below. |
| GitHub release downloads | v0.4.0 has a Node.js package and standalone files for macOS, Linux and Windows. |
| npm registry | @lockedinlabs/agent-console is not published. Use the source checkout or a published GitHub release archive. |
| Homebrew | The documented tap has not been verified as available. Use source or the listed GitHub release. |
| Published container image | A v0.4.0 image has not been verified. Do not assume the source version is an available image tag. |
Prefer npm install? npm can install a published GitHub archive even while
the registry name is unavailable. For the currently published v0.4.0:
npm install --global --ignore-scripts https://github.com/LockedinLabs-AI/agent-console/releases/download/v0.4.0/lockedinlabs-agent-console-0.4.0.tgz
agent-console --open
In Windows PowerShell use npm.cmd and agent-console.cmd.
If npm reports a permission error, use the source route; administrator access
is unnecessary.
These commands require lockedinlabs-agent-console-0.4.0.tgz to be listed
on the release page.
Until that file is published, use the source instructions above.
npx --yes https://github.com/LockedinLabs-AI/agent-console/releases/download/v0.4.0/lockedinlabs-agent-console-0.4.0.tgz --open
In Windows PowerShell, use npx.cmd because the default policy can refuse
npx's script form:
npx.cmd --yes https://github.com/LockedinLabs-AI/agent-console/releases/download/v0.4.0/lockedinlabs-agent-console-0.4.0.tgz --open
Published files can be checked against the release's SHA256SUMS and build
attestation (Checking a download). Consult that
version's release notes for its signing status. The Windows executable is
not code-signed; Node.js can run the source without installing that executable.
Behind a proxy or TLS inspection. npx, npm and curl use
HTTPS_PROXY; Node.js's own downloads, such as the check at the start of a
join command, use it only with NODE_USE_ENV_PROXY=1 as well (Node.js 22.21
or newer). Where the network inspects TLS, point Node.js at your company's
root certificate with NODE_EXTRA_CA_CERTS=<file>.pem. A join command that
stops with fetch failed on a company network needs these
(details).
To remove it, see Uninstall.
You need a Mac, a Linux machine or a Windows PC, and about two minutes.
Install Node.js 22 or newer. Get the LTS version from
nodejs.org. To check, open a terminal (Terminal on a
Mac, PowerShell on Windows) and type node --version — it should say
v22 or higher.
Without Node.js, the published v0.4.0 standalone downloads run this
console; see Install.
Start it. Paste this into the terminal and press Return:
git clone https://github.com/LockedinLabs-AI/agent-console.git
cd agent-console
node bin/agent-console.mjs --open
The same commands work in Windows PowerShell. They require Git; the Download ZIP instructions below work without it.
That starts the source checkout and opens it in your browser, signed in, normally at
http://127.0.0.1:6787. If that port is taken, the terminal prints the
address it used instead. Leave the terminal window open; closing it (or
pressing Ctrl+C) stops the console. The same command starts it again.
The first start reads the Claude Code and Codex history already on this computer. With months of it that can take a minute; the terminal counts the files as it goes, and so does the console.
No Node.js? The v0.4.0 release carries standalone executables with Node.js inside. Use the installation instructions and check the downloaded file.
Or download it. On the GitHub page,
press the green Code button, then Download ZIP, and unzip it. You get a
folder called agent-console-main. In a terminal, go into that folder and
start the console:
cd ~/Downloads/agent-console-main
node bin/agent-console.mjs --open
On Windows (PowerShell) the first line is cd $HOME\Downloads\agent-console-main.
If node then says it cannot find bin/agent-console.mjs, Windows unzipped
the folder inside another one of the same name: run cd agent-console-main
once more. (If you use git: git clone https://github.com/LockedinLabs-AI/agent-console.git,
then cd agent-console.)
The .tgz on the release page. The releases page
lists a file named lockedinlabs-agent-console-<version>.tgz. It is the
packaged console for that release; it does not track main. Source code (zip)
on the same page is that
release's code, used the same way as Download ZIP (its folder is named
agent-console-<version>).
The rest of this page writes commands as node bin/agent-console.mjs. If you
use a published package, put npx --yes <that release link> in its place,
and consult that version's README for supported features.
Nothing to install beyond Node, no account, no build step, no dependencies.
To loo