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

@jojoyo/codex-sdk

v0.44.0-fork.3

Published

TypeScript SDK for Codex APIs.

Readme

Codex SDK

Bring the power of the best coding agent to your application.

Installation

npm install @jojoyo/codex-sdk

Usage

Call startThread() and run() to start a thead with Codex.

import { Codex } from "@jojoyo/codex-sdk";

const codex = new Codex();
const thread = codex.startThread();
const result = await thread.run("Diagnose the test failure and propose a fix");

console.log(result);

You can call run() again to continue the same thread.

const result = await thread.run("Implement the fix");

console.log(result);

Streaming

The await run() method completes when a thread turn is complete and agent is prepared the final response.

You can thread items while they are being produced by calling await runStreamed().

const result = thread.runStreamed("Diagnose the test failure and propose a fix");

Resuming a thread

If you don't have the original Thread instance to continue the thread, you can resume a thread by calling resumeThread() and providing the thread.

const threadId = "...";
const thread = codex.resumeThread(threadId);
const result = await thread.run("Implement the fix");

console.log(result);

Working directory

By default, Codex will run in the current working directory. You can change the working directory by passing the workingDirectory option to the when creating a thread.

const thread = codex.startThread({
  workingDirectory: "/path/to/working/directory",
});

To avoid unrecoverable errors, Codex requires the working directory to be a git repository. You can skip the git repository check by passing the skipGitRepoCheck option to the when creating a thread.

const thread = codex.startThread({
  skipGitRepoCheck: true,
});