Platform · Agent runs
A run,not a reply.
Give it the matter and your instructions. It settles a plan, does the work, and comes back with something you can check before anything is acted on.
A run is a piece of legal work with a beginning and an end. It carries the matter, the jurisdiction, the tools it is permitted to use, and a record of every authority it touched. It survives a closed tab, it can be put on a schedule, and it queues for a person rather than acting on its own. That is the difference between an assistant that answers and one that finishes the job.
Planned before it searchesTool use you can seeApproval gateScheduled runsFull source record
Run · Northline employmentLive
InstructionsAdvise on the restrictive covenant and settle a reply to the letter before action
Plan6 lines of enquiry across statute, case law, and the file
Authorities12 consulted · 6 statutory · 4 judgments · 2 commentary
Verification11 propositions supported · 1 marked thin
Work productNote of advice drafted · awaiting your approval
The run holds until a person approves it
What happens between the instruction and the answer
It opens with the file loaded
The papers, the earlier research, the decisions taken, and your firm’s positions are already in front of it. You are not pasting the background into a prompt.It writes the plan first
The research plan is on the page before the first search runs. Narrow it, extend it, or change the jurisdiction, and it works to the version you approved.It retrieves and then verifies
Authority is found across statute, case law, filings, commentary, and your own papers. Each proposition is then checked against the passage said to support it, as a separate step.It stops before it acts
Anything that would send, file, or overwrite waits for you. You see the change before it lands, and refusing it costs nothing.
What a run gives you
- Work that continues after you close the tab, with the result waiting when you return
- Scheduled runs for recurring work such as a weekly docket sweep or a renewal check
- Depth you set per run, from a fast pass to a deep read across more sources
- Jurisdiction selection across ten jurisdictions, defaulting to a global view
- Tool use in the open: every search, fetch, document read, and edit is on the record
- Attachments read in place, including scans, through OCR
- An approval queue for anything that leaves the workspace
- A per-matter boundary, so a run cannot read outside the file it was given
Questions
About runs
- How is a run different from a chat message?
- A chat message returns text. A run plans, uses tools against real sources, checks its own support, produces a document, and records what it did. It has a state you can inspect while it is going and a result you can audit afterwards.
- Does it keep working if I close the browser?
- Yes. Runs execute on 8rney's workers, not in your tab. Close it, come back later, and the result and the full record are there.
- Can it send an email or file something without asking?
- No. Anything that sends, files, or overwrites queues for approval. You see the exact change before it applies, and nothing happens until a person approves it.
- What stops it inventing an authority?
- Retrieval and verification are separate steps. A claim is checked against the span of the source that supports it, and support the system cannot confirm is reported as thin rather than smoothed over.
- Can I see what tools it used?
- Yes. Every search, fetch, document read, and document edit appears in the run record, with the source behind it.
- Can a run read documents from another matter?
- No. Access follows the matter, including ethical walls. A run is scoped to the file it was given.