Anselm

How it works

From a Conversation to a Running Workflow.

This is the full path of one request, using real screens from the app. The request: every Monday at 09:00, collect the last two weeks of GitHub activity, write a digest, wait for approval, and file it in the Library.

  1. 1 · Describe the outcome

    You write one message. Anselm plans the work as a checklist, then creates each building block in order, reporting every tool call as a card you can open.

    You write one message. Anselm plans the work as a checklist, then creates each building block in order, reporting every tool call as a card you can open.You write one message. Anselm plans the work as a checklist, then creates each building block in order, reporting every tool call as a card you can open.

  2. 2 · The workflow exists

    A cron trigger, three parallel GitHub fetches, an Agent that writes the digest, a Control node that skips empty weeks, an approval node, a Function that files the document, and a Handler that announces it. Open the graph editor and every node shows its input mapping and retry policy; control nodes also show their routing branches.

    A cron trigger, three parallel GitHub fetches, an Agent that writes the digest, a Control node that skips empty weeks, an approval node, a Function that files the document, and a Handler that announces it. Open the graph editor and every node shows its input mapping and retry policy; control nodes also show their routing branches.A cron trigger, three parallel GitHub fetches, an Agent that writes the digest, a Control node that skips empty weeks, an approval node, a Function that files the document, and a Handler that announces it. Open the graph editor and every node shows its input mapping and retry policy; control nodes also show their routing branches.

  3. 3 · A run fails, then gets fixed

    An earlier run failed at fetch_commits with a 502 from GitHub. Anselm added retry with backoff to the Function, published version 2, and every later run used it. All runs stay in the matrix, including the failed one.

    An earlier run failed at fetch_commits with a 502 from GitHub. Anselm added retry with backoff to the Function, published version 2, and every later run used it. All runs stay in the matrix, including the failed one.An earlier run failed at fetch_commits with a 502 from GitHub. Anselm added retry with backoff to the Function, published version 2, and every later run used it. All runs stay in the matrix, including the failed one.

  4. 4 · A run waits for you

    The latest run collected 32 commits, wrote the digest, and parked at the approval node. The Gantt shows exactly where time went.

    The latest run collected 32 commits, wrote the digest, and parked at the approval node. The Gantt shows exactly where time went.The latest run collected 32 commits, wrote the digest, and parked at the approval node. The Gantt shows exactly where time went.

  5. 5 · Approve from the ledger

    The approval request is rendered in the notification ledger with the digest summary and counts. Approve, and the run resumes from that node.

    The approval request is rendered in the notification ledger with the digest summary and counts. Approve, and the run resumes from that node.The approval request is rendered in the notification ledger with the digest summary and counts. Approve, and the run resumes from that node.

  6. 6 · The draft is ready to publish

    The draft is already in Weekly digests, tagged draft, with an outline and backlinks. Approval publishes it. Next Monday the cron fires on its own.

    The draft is already in Weekly digests, tagged draft, with an outline and backlinks. Approval publishes it. Next Monday the cron fires on its own.The draft is already in Weekly digests, tagged draft, with an outline and backlinks. Approval publishes it. Next Monday the cron fires on its own.

Start Building Without Building the Stack.

DownloadRead the docs