Most agents can talk. Few can pay a vendor, keep last quarter in mind, or run three jobs at once without leaking a key. SaveMinute is the desk they sit at: payments, messaging, finance, memory, skills, secrets, cloning, parallel runs, and a sandbox around each one.
They forget the customer from Tuesday. They cannot send the invoice. They ask you for an API key in plain chat. They try two tools at once and step on each other. None of that is a model problem. It is missing furniture.
SaveMinute puts the furniture in. A place to keep memory that does not reset. A rail for money. A vault for secrets. A way to clone a working agent and run copies in parallel, each in its own sandbox. You still write the work. We keep the desk from falling over.
If an agent cannot pay, remember, or stay in its lane, it is a demo. Not a worker.
Nine tools. One workspace. Open a desk, drop an agent on it, and hand it only what the task needs. Full notes live on the toolkit page.
An agent that can write a perfect email and still cannot send an invoice is stuck. SaveMinute ties the three rails together. A message can become a payment. A payment writes a ledger line. The ledger is still there on Friday.
You set who they may pay, how much, and which inbox they speak from. The agent does the Tuesday work. You review the exceptions.
Open the money desk08:12 inbox-triage files 14 vendor notes. Three need a payment.
08:19 invoice-clerk checks memory for Northline terms. Net-15. Last paid on time.
08:21 secret scoped for 40 seconds. Payment sent. Receipt attached to the thread.
08:22 finance row posted. Clone of clerk starts a dry run on the next vendor.
Context windows end. Work does not. SaveMinute keeps a long file per agent and per desk: vendors, preferences, open loops, the joke a customer made in March that still matters.
The agent searches it. You can pin a fact, archive a season, or wipe a thread. Nothing important lives only in the last 20 messages.
Read the longer note on how memory is kept.
Prefers PDF invoices. Pays net-15. Contact is Priya on billing@northline. Do not CC the whole office.
Ledger-watch still owes a variance note on account 4402. Started 2 Sep. Owner: clone-of-clerk.
A skill is a named package: how to file a tax row, how to talk to a carrier, how to close a ticket. You attach it to an agent. You bump the version. You revoke it when the process changes.
Clones do not silently inherit every skill. You pick the set. That keeps a sandbox clone from acting like payroll.
The vault holds tokens, account numbers, and signing keys. An agent requests a secret by name. The desk grants a short lease. The value never lands in memory as a quote you can copy later.
If a run looks wrong, you cut the lease. Details on the security page.
One good agent should not be a bottleneck. Copy it. Point the copies at different piles. Watch them in parallel. If one goes odd, the sandbox holds the mess.
Copy memory, skills, and limits. Or copy only the skills and start a clean file. Name the clone so the log stays honest.
Queue jobs across clones. The desk shows who is paying, who is waiting, and who is still in a dry run.
Network, files, and spend are fenced. A clone testing a new skill does not touch live rails unless you say so.
No ceremony. You open the workspace, wake the agents that own the pile, and stay for the exceptions.
Start a sessionPick a workspace. Yesterday’s memory is still there. Secrets stay in the vault until a run asks.
Give the agent the packages it needs. Cap payments. Choose the inbox it may speak from.
One clerk for Northline, a clone for the rest. Parallel runs, separate logs.
Sandbox status stays visible. If a run reaches for a key it should not have, the lease fails closed.
Invoice piles, vendor chatter, the same three exceptions every week. Agents take the pile. People take the weird ones.
Reconciliation is a long memory problem. The desk keeps the file, posts the row, and shows the variance without a new chat each time.
Clone a good responder. Point copies at queues. Messaging stays on-brand because the skill is versioned.
You do not need a platform team to give one agent a vault, a sandbox, and a way to pay a bill. Open the workspace and start.
More on the FAQ. You do not need a platform team. New clones start in dry run. An agent gets memory, skills, a vault lease, rails you enabled, and a sandbox.
No. If you can open a browser and name an agent, you can sit it at this desk. Harder rails (live payments, production secrets) wait until you turn them on.
Yes. Dry run is the default for new clones. Live rails stay off until you flip them for that agent.
Open a workspace. Name an agent. Hand it memory, a skill, and a fence. If it needs to pay someone or answer a thread, the rails are on the same desk.