Box File Intake Agent with OpenCode

The comment has to be written for the reviewer who opens this file in three years, not for the colleague who uploaded it this morning: the class it matched, the exact fragment of name or path it matched on, and what a person still owes before the file counts as complete. OpenCode is simple to aim at a shape that fixed, and changing the engine behind it does not change the shape.

Loading preview…
Free to start · guided setup

Watch it work before it's live

Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.

MSA_Executed_Vantage-Kliniken-GmbH_2026-08-11.pdf

Priya Raghunathan, Legal Operations/Legal/Contracts/2026/Executed

PDF, 1.8 MB, uploaded 16:42 CET through the e-signature connector. Four other files here begin with MSA_Executed_ and carry a counterparty and a date in the same shape. The folder is collaborated on by the legal group only.

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect Box

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Filing rules

    What each kind of document is called in your Box and where it is supposed to live - the folders you watch, the naming patterns that identify contracts, invoices, onboarding forms and the rest, what each class still needs before it counts as complete, and who gets pinged for which.

  4. Runs on OpenCode

    Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.

  5. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

Why OpenCode for this agent

Written for a stranger later

Audit questions arrive long after everyone involved has moved on. A comment that names its own reasoning survives that, where a Slack thread and an uploader's memory do not.

The matched fragment, quoted

Recording that MSA_Executed_ was the part that decided it lets a human check the decision in a second, and lets you spot a naming convention drifting before it breaks the rules.

Before you fork

Comments accumulate. What happens on a file that is re-uploaded?

A new version is a new event and produces a new comment, so a document uploaded four times carries four of them. As an intake record that is deliberate, but it does read as noise in folders where people iterate on drafts. Watch the folders where arrival is the meaningful moment and leave the drafting ones alone.

Run it with a different agent

Put Box File Intake Agent to work on OpenCode

Free to start. Guided setup, a test run against staged conversations, and it's live.