Mola LedgerEARLY ACCESSGet started ↗
SMALL SDK. CLEARER PICTURE.

Your agents act.
You stay in control.

See what your AI agents do. Catch duplicate actions.
Investigate the unexpected—all from one local dashboard.

$npm install mola-ledger

No account. No ledger API key. No extra services.

● ● ●
mola / studio Runs locally
Mola Ledger Studio showing four attempts, two unique operations, two suppressed attempts and one uncertain outcome
MOLA STUDIO Actual dashboard · sample activityView full size ↗
↗

Know what happened.

Follow agent actions, execution attempts, and outcomes in a single, searchable history.

⤴

Catch the repeats.

Recognize the same intended action and return its confirmed result without running it again.

⌕

Find what needs you.

When an outcome is uncertain, block blind retries and keep the evidence ready for review.

A small wrapper.
A lot more clarity.

Keep your agent. Keep your tools. Wrap the actions that matter, then open Studio to see their history.

  1. 01

    Install Mola Ledger

    Add the package to your Node.js application.

  2. 02

    Protect an action

    Give it a stable ID that stays the same on retries.

  3. 03

    Open your dashboard

    See attempts, repeats, and outcomes as they happen.

Read the quick start ↗
protect-action.jsJavaScript
import { createLedger } from 'mola-ledger';

const ledger = createLedger();

// Same intended action. Same ID.
const incident = await ledger.execute({
  id: 'incident-for-alert-1842-v1',
  action: 'incident.create',
  input: { alertId: 1842 },
  run: ({ idempotencyKey }) =>
    provider.createIncident({
      alertId: 1842,
      idempotencyKey,
    }),
});

Integration example: provider is your existing client. Close the ledger during application shutdown.

A retry shouldn't
be a leap of faith.

Explore what happens when your agent calls the same protected action again.

CONFIRMED

Action completed. Result recorded.

The first call runs your action and saves its confirmed result. You can inspect the operation and its history in Studio.

ILLUSTRATIVE OPERATION
incident-for-alert-1842-v1
Agent request→ Execute action
Ledger decisionSave confirmed result ✓

Protection applies to wrapped calls using the same stable identity and shared local ledger. Mola Ledger does not guarantee exactly-once external execution.

Local today.
More connected tomorrow.

Start with a dashboard that lives alongside your application. No extra service to manage.

SDK + local Studio

AVAILABLE NOW

Monitor and protect actions in your Node.js app. Search operations, follow timelines, and investigate uncertain results.

Centralized monitoring

PLANNED

A shared view across deployed agents, with an open-source, self-hosted server package. Follow development and releases on GitHub.

Make your agents
easier to trust.

Install the SDK. Wrap an action. Open Studio.

01 / INSTALLnpm install mola-ledger
02 / OPEN STUDIOnpx mola-ledger studio

Node.js 22.16+ · Wrap your action between these steps.
Before npm release, use the source installation in the quick start.

Follow the quick start ↗

Explore the code.
Help shape what’s next.

Mola Ledger lives on GitHub. Read the source, try the examples, report an issue, or contribute an improvement.

View on GitHub ↗
zaiderikat

Mola-Ledger

PUBLIC REPOSITORY

A lightweight agent action ledger with duplicate protection and a built-in local dashboard.

Explore the latest activity on GitHub.

A few things to know.

Does it work with my agent framework?

Mola Ledger is a framework-neutral Node.js SDK. Wrap your tool functions with ledger.execute(). The documentation includes an OpenAI Agents SDK and GitHub Issues example. Calls that bypass the wrapper are not tracked or protected.

What happens if an action times out?

A timeout may mean the external service acted but its reply was lost. Mola Ledger records the uncertain outcome and blocks blind retries. Verify the result with the provider, then reconcile through the SDK.

Where does my activity stay?

The local ledger stays on your machine. Studio is a read-only dashboard available on localhost. It is not designed to be exposed to the public internet.

Can I monitor multiple servers today?

The current release coordinates through one local ledger. It does not coordinate independent hosts or serverless instances. A compatibility HTTP backend exists for small single-host evaluation; centralized remote monitoring is planned.