How Pileless works
Pileless sits between your autonomous agents and you. The agent does the work; Pileless collects the calls a human should make and hands them over on a clean plate.
Piles and items
There are two things to know:
- A pile is one batch of decisions an agent sends you.
- An item is one decision inside it — approve this, pick one of these, rank these, fill this in.
Three logo options to choose from? That's one pile, three options on one item. Five refunds to approve? One pile, five items. Everything an agent needs your call on lands in your inbox, sorted.
The loop
- The agent piles. Instead of stopping to ask (or worse, guessing), your agent calls
pile.createwith the decisions and keeps working or waits. - You clear the plate. Open your inbox whenever. Blocking items up top, fastest-to-slowest below — or your own dragged order. Decide in place.
- The decision flows back. Each call returns to the agent as structured data, so the workflow resumes itself. No copy-paste, no babysitting.
Decision types
| Type | The human does |
|---|---|
| Approve / reject | Yes-or-no on one thing (a draft, a refund, a deploy). |
| Pick one | Choose one option from several (subject lines, logos, designs). |
| Pick & mix | Keep any subset of options. |
| Rank | Order options best-to-worst. |
| Fill in / answer | Supply a value or a short answer the agent needs. |
| Direct edit | Tweak the text in place and send it back. |
Bring your own brain
Pileless runs no AI of its own. Your agent — on your key, your model — is the brain. Pileless exposes typed slots the agent fills (a summary of the ask, a suggested action, priority, tags), then renders and enforces. A suggestion is never an execution: it's a one-click pre-fill you confirm. The human always makes the call.
Agent clearance
Once your agent can drive, it's an actor with its own clearance — separate from your access, and default-deny. You grant it in steps: metadata only → the ask's content → attachments → decision history. It can triage "a high-sensitivity approval is blocking you" without being allowed to read the document. Redaction happens on our server; every access is audited. See Security for the full picture.