open-index/open-npm huggingface dataset:
npm package: @stigmergy/core
Description: Pressure-field scheduling for multi-agent AI systems. Zero dependencies, pure TypeScript.
Latest version: 0.2.0

# @stigmergy/core

**Your multi-agent system doesn't need a manager. It needs a pressure field.**

Most agent orchestration boils down to three bad options: polling on timers (wasteful), hardcoded if/else routing (brittle), or burning an LLM call to pick who goes next (slow and expensive). All three put coordination logic outside the system it's coordinating.

Stigmergy replaces them with a single primitive: a pressure field. Events deposit signals. Signals decay over time. When accumulated pressure crosses a threshold, the agent wakes and does the work. Dependencies resolve themselves through completion signals. Failed tasks create retry pressure automatically.

9.5x faster than LangGraph at 120 tasks / 30 agents. Scheduling overhead stays sub-millisecond at 1,000+ tasks -- the ceiling is your LLM API throughput, not the scheduler. Region-indexed storage and bounded signal accumulation mean it doesn't degrade as agent pools grow.

Zero dependencies, pure TypeScript. See the [main repo](https://github.com/Production-Grade/stigmergy) for full benchmarks, scaling characteristics, and integration guides.

## Install

```bash
npm install @stigmergy/core
```

## Quick start

```typescript
import { StigmergyScheduler } from "@stigmergy/core";

const scheduler = new StigmergyScheduler({
  tickIntervalMs: 1000,
  defaultWakeThreshold: 0.4,
});

scheduler.setDispatcher(async (agentId, task) => {
  // your agent logic here
  return { success: true };
});

scheduler.addTask({
  id: "draft",
  description: "Write first draft",
  agentId: "writer",
  dependencies: [],
  priority: 0.8,
});

scheduler.addTask({
  id: "review",
  description: "Review the draft",
  agentId: "reviewer",
  dependencies: ["draft"],
  priority: 0.6,
});

scheduler.start();
```

## Low-level field

For custom scheduling logic, use `PressureField` directly:

```typescript
import { PressureField } from "@stigmergy/core";

const field = new PressureField({
  decayHalfLifeSeconds: 300,
  evaporationThreshold: 0.01,
});

field.deposit({ agentId: "system", signalType: "event", intensity: 0.8, targetAgentId: "writer" });
field.decay();
const pressure = field.readPressure("writer");
```

## Author

Built by [Warwick McIntosh](https://github.com/warwickmcintosh) at [Production Grade](https://blog.productiongrade.tech).

- GitHub: [warwickmcintosh](https://github.com/warwickmcintosh)
- X: [@warwickmcintosh](https://x.com/warwickmcintosh)
- Email: contact@productiongrade.tech
- Blog: [blog.productiongrade.tech](https://blog.productiongrade.tech)

## License

MIT
npm package: @stigmergy/nemoclaw-scheduler
Description: Stigmergy pressure-field scheduling plugin for OpenClaw / NemoClaw
Latest version: 0.2.0

# @stigmergy/nemoclaw-scheduler

**Zero-code pressure-field scheduling for [NemoClaw](https://github.com/NVIDIA/NemoClaw).** Install the plugin, add config, restart. Your agents get task scheduling with dependencies, priorities, and automatic retry. No code changes required.

Scheduling overhead is sub-millisecond regardless of agent count. Scales to thousands of tasks without configuration changes -- the bottleneck is your LLM provider, not the scheduler.

## Install

```bash
git clone https://github.com/Production-Grade/stigmergy.git
nemoclaw plugins install ./stigmergy/packages/nemoclaw
```

Add to your `nemoclaw.json`:

```json
{
  "plugins": {
    "entries": {
      "stigmergy-scheduler": {
        "enabled": true,
        "config": {
          "tickIntervalMs": 5000,
          "defaultWakeThreshold": 0.4,
          "decayHalfLifeSeconds": 300,
          "evaporationThreshold": 0.01
        }
      }
    }
  }
}
```

Restart NemoClaw. You should see:

```
Stigmergy scheduler started (tick=5000ms, threshold=0.4)
```

## What you get

**4 agent tools:**

| Tool | Description |
|------|-------------|
| `stigmergy_add_task` | Queue a task with dependencies and priority |
| `stigmergy_inject_urgent` | Force-inject a high-priority task |
| `stigmergy_status` | View scheduler metrics |
| `stigmergy_deposit_signal` | Manually deposit a pressure signal |

**Hooks:** `agent_end` deposits activity signals for natural pressure accumulation.

**Gateway methods:** `stigmergy.metrics`, `stigmergy.pressure`

## Status

NemoClaw is in early preview (alpha). This plugin tracks the NemoClaw plugin API which may have breaking changes between releases.

## License

MIT
npm package: @stigmergy/openclaw-scheduler
Description: Stigmergy pressure-field scheduling plugin for OpenClaw
Latest version: 0.2.0

# @stigmergy/openclaw-scheduler

**Zero-code pressure-field scheduling for [OpenClaw](https://github.com/openclaw/openclaw).** Install the plugin, add config, restart. Your agents get task scheduling with dependencies, priorities, and automatic retry. No code changes required.

Scheduling overhead is sub-millisecond regardless of agent count. Scales to thousands of tasks without configuration changes -- the bottleneck is your LLM provider, not the scheduler.

## Install

**Step 1 — Clone this repo and install the plugin:**

```bash
git clone https://github.com/Production-Grade/stigmergy.git
openclaw plugins install ./stigmergy/packages/openclaw
```

**Step 2 — Add this to your `openclaw.json`:**

```json
{
  "plugins": {
    "entries": {
      "stigmergy-scheduler": {
        "enabled": true,
        "config": {
          "tickIntervalMs": 5000,
          "defaultWakeThreshold": 0.4,
          "decayHalfLifeSeconds": 300,
          "evaporationThreshold": 0.01
        }
      }
    }
  }
}
```

> Not sure where your config file is? Run `openclaw config path` to find it.

**Step 3 — Restart OpenClaw.**

You should see this in the logs:

```
Stigmergy scheduler started (tick=5000ms, threshold=0.4)
```

Run `openclaw plugins list` to confirm the plugin shows as `loaded`.

## What you get

**4 agent tools:**

| Tool | Description |
|------|-------------|
| `stigmergy_add_task` | Queue a task with dependencies and priority. Dispatched when pressure exceeds threshold. |
| `stigmergy_inject_urgent` | Force-inject a high-priority task for immediate processing. |
| `stigmergy_status` | View scheduler metrics — pressure per agent, pending tasks, completions. |
| `stigmergy_deposit_signal` | Manually deposit a pressure signal (e.g., from an external event). |

**Hooks:**
- `agent_end` — deposits activity signals when any agent run completes, creating natural pressure accumulation.

**Gateway methods:**
- `stigmergy.metrics` — full scheduler metrics snapshot
- `stigmergy.pressure` — per-agent pressure map and signal count

## Config options

| Option | Default | Description |
|--------|---------|-------------|
| `tickIntervalMs` | `5000` | How often the scheduler evaluates and dispatches (ms) |
| `defaultWakeThreshold` | `0.4` | Minimum pressure to wake an agent (0.0–1.0) |
| `decayHalfLifeSeconds` | `300` | Half-life for signal decay |
| `evaporationThreshold` | `0.01` | Signals below this are removed |

## How it works

Instead of cron-based scheduling, agents wake when accumulated pressure from deposited signals exceeds a threshold. Signals decay exponentially over time (like pheromones). Task completions deposit new signals that trigger dependent work.

See the [main README](../../README.md) for the full explanation and benchmarks.

## License

MIT
npm package: @stijlbreuk/prettier-config
Description: A global Prettier config to be used in Stijlbreuk projects
Author: Stijlbreuk
Latest version: 1.5.3

# `@stijlbreuk/prettier-config`

## Table of Contents

- [Installation](#installation)
- [Usage](#usage)
  - [`package.json`](#packagejson)
  - [Prettier config](#prettier-config)

## Installation

To install the package, simply choose your package manager of choice and install `@stijlbreuk/prettier-config`.

For example with npm:

```bash
$ npm install --save-dev @stijlbreuk/prettier-config
```

## Usage

When installed, to use the config you will need to configure prettier to do so.

The following options are available:

### `package.json`

In your `package.json` add the `prettier` key followed by the package name:

```json
{
  "name": "package-name",
  "version": "1.0.0",
  "prettier": "@stijlbreuk/prettier-config"
}
```

### Prettier config

In your prettier config, albeit `.prettierrc` or `prettier.config.js` etc., simply have it be

```
"@stijlbreuk/prettier-config"
```

or to extend the config

```
module.exports = {
	...require('@stijlbreuk/prettier-config'),
	useTabs: true
}
```
npm package: @stijlbreuk/standard-sentry-setup
Description: [![npm version](https://badge.fury.io/js/standard-sentry-setup.svg)](https://www.npmjs.com/package/standard-sentry-setup)
Author: Sajjad Shirazy
Latest version: 1.1.2

# Sentry Standard Setup

[![npm version](https://badge.fury.io/js/standard-sentry-setup.svg)](https://www.npmjs.com/package/standard-sentry-setup)

Initializes Sentry in a standard way using environment values.

## Features

- Express integration
- HTTP requests tracing
- Excluding Prometheus requests
- Handling environments
- Handling Sentry releases feature using Git short SHA key

## Install

```bash
npm i standard-sentry-setup
```
npm package: @stijndepestel/create-with-template
Description: NPM starter to create a project from a template
Author: Stijn De Pestel
Latest version: 0.0.2

# @stijndepestel/create-with-template

NPM starter command to kick-start your node project.

> NOTICE: This release is still in a beta phase.

When executing the command, you'll be asked to either select on of the templates that are provided for you, or to provide a custom template from a git repository.

You can execute the command by running

```bash
npx @stijndepestel/create-with-template
```

There is a `--help` flag available to get more information about the usage of the command.