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

@morphixai/agent-workspace

v1.0.1

Published

Runtime-private workspace with commit semantics for agent runtimes — staging area + in-memory store.

Readme

@morphixai/agent-workspace

Sandbox — the restricted operating environment an agent instance is constructed with — plus the storage ports it builds on.

An agent never touches host storage directly: every file/data operation goes through its injected Sandbox. Two instances with different sandboxes are mutually unreachable by construction (the isolation is structural, not policy-based).

Install

npm install @morphixai/agent-workspace

Sandbox hierarchy

import { Sandbox, VirtualSandbox, LogicalSandbox } from '@morphixai/agent-workspace';

// zero-dependency, in-memory — tests / demos / ephemeral agents
const sandbox = new VirtualSandbox();
await sandbox.files.write('report.md', '# Draft');

// production: subclass LogicalSandbox and bind real adapters at construction
class AppSandbox extends LogicalSandbox {
  constructor(deps: { cos: CosClient; appData: AppDataService }) {
    super({ files: cosFilePort(deps.cos), data: appDataPort(deps.appData) });
  }
}
  • Sandbox (abstract) — implements the Workspace contract; declares its isolation level: virtual | logical | process | container.
  • VirtualSandbox — in-memory, zero deps. The default for tests and demos.
  • LogicalSandbox — construction-bound ports over your real storage (object storage, DB, …). Per-app/per-user boundaries live in the adapters.

Lifecycle note: disposing an agent instance does not drop its sandbox — sandboxes are host-owned and may outlive (or be shared across) instances the host constructs.

Storage ports

Backing stores usable standalone or inside a sandbox:

  • InMemoryStore — in-memory backing store.
  • JsonFileStore — file-backed store (handy for local persistence in tests).
  • Types: Workspace, WorkspaceContent, WorkspaceEntry, WorkspaceKind, CommitTarget, WorkspaceError / WorkspaceErrorCode.

Pairs with @morphixai/agent-framework (instances are constructed with a sandbox) but is usable standalone.

Versioning

≥ 1.0.0 is the framework-v2 stable line, released in lockstep with agent-core / agent-bus / agent-framework. The pre-1.0 "runtime-private staging workspace" framing evolved into the Sandbox model above.

License

MIT © MorphixAI