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

@reminix/langgraph

v0.0.22

Published

Reminix agents for LangGraph - serve AI agents as REST APIs

Downloads

282

Readme

@reminix/langgraph

Reminix agents for LangGraph. Serve any LangGraph agent as a REST API.

Ready to go live? Deploy to Reminix Cloud for zero-config hosting, or self-host on your own infrastructure.

Installation

npm install @reminix/langgraph @langchain/langgraph

This will also install @reminix/runtime as a dependency.

Quick Start

Thread Agent (chat-style)

import { createReactAgent } from '@langchain/langgraph/prebuilt';
import { ChatOpenAI } from '@langchain/openai';
import { LangGraphThreadAgent } from '@reminix/langgraph';
import { serve } from '@reminix/runtime';

const llm = new ChatOpenAI({ model: 'gpt-4o' });
const graph = createReactAgent({ llm, tools: [] });
const agent = new LangGraphThreadAgent(graph, { name: 'my-agent' });
serve({ agents: [agent] });

Workflow Agent (multi-step with interrupt/resume)

import { LangGraphWorkflowAgent } from '@reminix/langgraph';
import { serve } from '@reminix/runtime';

const graph = buildWorkflowGraph(); // your LangGraph compiled graph
const agent = new LangGraphWorkflowAgent(graph, { name: 'my-workflow' });
serve({ agents: [agent] });

Your agent is now available at:

  • POST /agents/{name}/invoke - Execute the agent

API Reference

new LangGraphThreadAgent(graph, options?)

Create a LangGraph thread agent for chat-style interactions.

| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | graph | CompiledGraph | required | A LangGraph compiled graph | | options.name | string | "langgraph-agent" | Name for the agent (used in URL path) | | options.description | string | "langgraph thread agent" | Description shown in agent metadata | | options.instructions | string | — | System instructions prepended to messages | | options.tags | string[] | — | Tags for categorizing/filtering agents | | options.metadata | Record<string, unknown> | — | Custom metadata merged into agent info |

Returns: LangGraphThreadAgent - A Reminix thread agent instance

The thread agent:

  1. Converts incoming messages to LangChain message format
  2. Prepends a SystemMessage if instructions is set
  3. Invokes the graph with { messages: [...] }
  4. Extracts the last AI message from the response
  5. Returns it in the Reminix response format

new LangGraphWorkflowAgent(graph, options?)

Create a LangGraph workflow agent for multi-step execution with interrupt/resume support.

| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | graph | CompiledGraph | required | A LangGraph compiled graph | | options.name | string | "langgraph-workflow-agent" | Name for the agent (used in URL path) | | options.description | string | "langgraph workflow agent" | Description shown in agent metadata | | options.instructions | string | — | Stored in metadata (not injected into graph execution) | | options.tags | string[] | — | Tags for categorizing/filtering agents | | options.metadata | Record<string, unknown> | — | Custom metadata merged into agent info |

Returns: LangGraphWorkflowAgent - A Reminix workflow agent instance

The workflow agent:

  1. Streams the graph and collects per-node outputs as steps
  2. Maps GraphInterrupt to pendingAction with status "paused"
  3. Accepts resume input to continue interrupted graphs via Command
  4. Returns structured {status, steps, result?, pendingAction?} output

Endpoint Input/Output Formats

Thread Agent — POST /agents/{name}/invoke

Request:

{
  "input": {
    "messages": [
      {"role": "user", "content": "Hello!"}
    ]
  }
}

Response:

{
  "output": "Hello! How can I help you today?"
}

Workflow Agent — POST /agents/{name}/invoke

Request:

{
  "input": {"task": "process data"}
}

Response:

{
  "output": {
    "status": "completed",
    "steps": [
      {"name": "fetch_data", "status": "completed", "output": {"records": 10}},
      {"name": "process", "status": "completed", "output": {"summary": "done"}}
    ],
    "result": {"summary": "done"}
  }
}

Resume a paused workflow:

{
  "input": {
    "task": "process data",
    "resume": {"step": "approve", "input": {"approved": true}}
  }
}

Streaming

For streaming responses (thread agent only), set stream: true in the request:

{
  "input": {
    "messages": [{"role": "user", "content": "Hello!"}]
  },
  "stream": true
}

The response will be sent as Server-Sent Events (SSE).

Runtime Documentation

For information about the server, endpoints, request/response formats, and more, see the @reminix/runtime package.

Deployment

Ready to go live?

Links

License

Apache-2.0