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

cortex-orchestrate

v0.1.0

Published

Memory-first multi-agent orchestration SDK — built on mem0

Readme

cortex-orchestrate

Memory-first multi-agent orchestration SDK — built on mem0.

npm install cortex-orchestrate

Quick start

import Cortex from 'cortex-orchestrate'

const cortex = new Cortex({
  apiUrl: 'https://your-cortex-api.onrender.com',
  userId: 'user-123',
})

const canvas = cortex.canvas('job-screener')

// Run an agent pipeline
const result = await canvas.run({
  trigger: 'Evaluate candidate: Jane Doe, 5 yrs Python, AWS certified',
})

console.log(result.output)
console.log(`Memories written: ${result.memoriesWritten}`)

// Fetch accumulated memories
const memories = await canvas.memories()

// Search memories semantically
const relevant = await canvas.search({ query: 'Python candidates', limit: 5 })

How it works

Every canvas in Cortex is a named memory namespace (userId::canvasId). Agents write to and read from this namespace across runs — so each execution is informed by everything that came before it.

Run 1 → cold start → agents evaluate → write memories
Run 2 → warm start → agents recall Run 1 patterns → write delta memories
Run N → deep context → quality compounds

API

new Cortex(config)

| Option | Type | Description | |--------|------|-------------| | apiUrl | string | Your Cortex API base URL | | userId | string | User identifier for memory scoping | | apiKey | string? | Optional bearer token |

cortex.canvas(id)

Returns a Canvas instance scoped to that id.

canvas.run(options)

Executes the agent pipeline with the given trigger string. Returns { executionId, output, memoriesWritten, agentsRun }.

canvas.memories()

Returns all memories accumulated in this canvas namespace.

canvas.search({ query, limit?, agentId? })

Semantic search over canvas memories.

canvas.clearMemories()

Deletes all memories in this canvas namespace.

License

MIT © 2026