npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@aexhq/brain

v2.3.0

Published

Typed client for Brain sessions, tools, checkpoints, and event streams

Readme

Brain JavaScript and TypeScript SDK

Install with npm install --save-exact @aexhq/[email protected]. Requires Node.js 24+; there are no runtime dependencies. JavaScript and TypeScript use the same package.

import { Pi, Brain, Model } from '@aexhq/brain';

const brain = new Brain('http://127.0.0.1:8080', process.env.BRAIN_API_KEY);
const session = await brain.create({
  harness: Pi(), model: Model('openai/gpt-4.1-mini'), tools: [],
});
const input = await brain.send(session.id, { type: 'user.message', text: 'Hello!' });
for await (const event of brain.observe(session.id)) {
  if (event.type === 'assistant.message') console.log(event.data.text);
  if (event.input_id !== input.id) continue;
  if (event.type === 'session.error') throw new Error(event.data.message);
  if (event.type === 'session.status' && event.data.status === 'idle') break;
}

Tokens belong in a trusted backend. Requests are never automatically retried. BrainError exposes HTTP status, error code, and request ID. Stopping observation closes the stream; call interrupt(id) to interrupt execution. Reconnect with observe(id, { after: cursor, signal }) using the last retained event cursor.

Pass Tool({ name, description, input_schema, run }) in tools to run functions in your client. Select installed tools with ManagedTool(name). Supply private model credentials with Model(name, ApiKey(key)) or CredentialReference(reference); the server needs independent encryption keys.

The SDK owns SSE/HTTP or WebSocket callback connections; function source and captured credentials stay local. Keep the process alive and call dispose() on shutdown. After recovery, rebind() attaches matching functions without replaying actions.

Version 2 uses session bindings and structured result schemas. Update the server, runner, and client together, and pin the matching release commit.

SDK reference · Server setup