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

@string-os/string

v0.1.3

Published

String runtime — an OS for AI agents, built on SFMD

Readme

@string-os/string

String runtime — an OS for AI agents, built on SFMD. HTML for humans, SFMD for agents.

Browse documents, install apps, execute actions, navigate the web — all through Markdown. Drives a long-running daemon (stringd) so multiple agent calls share session state, history, and authentication.

Install

npm install -g @string-os/string

This installs three things:

  • string — CLI you call from a shell or an agent's shell tool
  • stringd — daemon that backs the CLI (auto-started; manage with string --daemon)
  • a Node library if you want to embed the runtime instead of shelling out

CLI

The basic shape is string <topic> '<command>'. A topic is one of:

  • a bare name (main, notes, setup) — a free-form session for ad-hoc work
  • app:<pkg>[:<config>] — an installed app session (e.g. app:weather)
  • bash:<name> — a persistent shell session (each name = its own pty)
  • app, bash, tool, system — hub topics that aggregate / manage their kind
# Install an app from a local file or URL
string setup '/install --app ./apps/weather/string.md'

# Open the app and call its actions
string app:weather '/open app:weather'
string app:weather '/act.now Seoul'
string app:weather '/act.forecast Tokyo'

# Open a web page in a free-form tab (rendered as Markdown)
string docs '/open https://developer.mozilla.org'

# Bash session
string bash:dev 'cd ~/work && ls'

# Hub view — aggregates installed apps, current sessions, etc.
string app

# REPL mode — drop the command argument
string app:weather

Output is wrapped in a short envelope so a calling program can tell runtime output apart from shell noise:

<𝒞=string:app:weather>
seoul: Sunny +20°C ↘6km/h
</𝒞>

Use --json for {ok, code, content, meta} JSON instead.

Daemon

The daemon starts automatically on first call. Manage it explicitly with:

string --daemon start
string --daemon status
string --daemon stop

Default port is 3100 (override with STRINGD_PORT). Sessions, env vars, and installed apps live under ~/.string/users/{user}/.

Library

import { Browser } from '@string-os/string';

const browser = new Browser({ home: process.cwd() });
const result = await browser.exec('/open ./README.md');
console.log(result.ok, result.content);

For talking to an already-running daemon from another language or process, use @string-os/client instead — it's lighter and has zero runtime dependencies.

Using from an agent

Any agent framework with a shell tool (Claude Code, OpenClaw, etc.) can drive string with no custom integration. One paragraph in the prompt is enough:

You have string installed. It's a Markdown browser with installable apps. Call it as string <topic> '<command>'. Output sits between <𝒞=string:topic> and </𝒞>. To find what an app can do: /open app:<name>. Currently installed: weather.

For richer integration, install the MCP server: @string-os/string-mcp.

Environment

| Variable | Default | Purpose | |---|---|---| | STRINGD_PORT | 3100 | Daemon listen port | | STRINGD_USER | default | User identity (multi-user daemons) | | STRINGD_HOME | ~/.string/users/{user} | Per-user data root (config, apps, env vars) |

/set $VAR = "value" persists vars to disk under the current scope (global, app, or app:config). Apps declare what they need with requires: in frontmatter; missing values surface as a hint at /open time.

Documentation

Related

License

MIT