Skip to content

@jori answers in Slack, GitHub, Linear, and more

The shared drive your AI works out of.

Put the jobs nobody wants next to the tables and files they keep current, in folders shaped like your teams and projects. Who can see a folder, and what it costs to run, come with it.

Slack#financeCopperline
ML

Maya Lund09:12

@jori add Harbor House to the renewals table, Sep 24, and flag it at risk.

JoriAPP09:12

Done. One row added, marked at risk. will keep it current.

Hand over the work nobody wants

Every company runs on chores: the weekly summary, the invoice chase, the ticket triage, the changelog. Write each one down once. Jori runs it on a schedule or when something happens, and files what they made where the team can find it.

Jobs

TriggerTools
WeeklyFri 16:006 toolsEngineering
JBJonas Berg
3d agoin 19h
EventGitHub4 toolsEngineering
LALiv Andersen
4m ago
EventLinear4 toolsEngineering
RMRavi Menon
26m ago
Daily07:001 toolWeb access allowedMarketing
ILIda Lindqvist
5h agoin 10h
WeeklyThu 10:004 toolsMarketing
OFOmar Farouk
6d agoin 6d
Daily07:001 toolRenewals
MLMaya Lund
5h agoin 10h
Chase overdue invoicesSpecific teams · 1 team
WeeklyMon 08:001 toolRenewals
PNPriya Natarajan
2h agoin 3d
Weekdays09:004 toolsDesign
HEHanna Ek
2d ago

Showing 1–8 of 8 matching jobs

Jobs are just instructions

Describe the job the way you'd brief a person. Type @ to give it access, / to load a skill, # to name a tool. Pick when it runs: a schedule, a date, or an event in Slack, GitHub, Linear, or Notion. It runs in the cloud whether or not your laptop is open.

Plain text, not pipelines
No node graphs, nothing to wire. If you can write the brief, you've written the job.
Only the access you gave it
Grants are per job. Web search is off until you turn it on.
Filed like anything else
A job lives in a folder. Move it, and the new folder decides who sees it and where its runs are counted.

Work lands where you can find it

A job doesn't answer in a chat window. It writes rows to a table, a value to a store, a file to a folder. You and Jori edit the same materials, so anything they keep current is something you can check and correct.

Tables
Typed columns, a grid people edit by hand, CSV in and out.
Stores
One JSON document under a schema you define. The state a job carries between runs.
Files
Anything, viewed in place: a PDF, an image, a page of notes. Jori saves what they make and marks it as their own.
1
2
3
4

4 rows

Every folder has a bill

Spend lands where the job is filed, so a team's total is its folder's total and a job's total is one row. Open Usage on any folder to see spend by subfolder and by source over the window you choose. A metered bill, not a report Jori writes about their own work.

By team
Engineering, Marketing, Finance: whatever your folders are called, that's what the bill is called.
By source
Each row is a job, or work someone asked for directly, with runs and cost per run.
Down to the run
Every number opens to the runs behind it, and the statement links each charge to its run.
No seats, no markup
One price for the organization. Model work at the provider's list rates, from prepaid credit with a cap you set.

Share it like a drive

Only me, specific people, specific teams, or everyone in the organization. Set it on an item, or set it on the folder and everything inside answers to it. For people outside, send a link that expires.

The folder is the ceiling
Nothing inside a folder reaches further than the folder does, whatever it's set to. The tree is a true map of who sees what.
Teams are an audience
Group the people who work together once. Then a folder, a table, or a job is shared with the team, not a list of names.
Links with a clock
A share link opens a read-only page without signing in, and expires on a clock you choose. Revoke it any time.
VisibilityWho in Copperline sees the Customer renewals table

Visible to . Narrowed to Finance by the folder it's in.

Share linksThe same table, for people outside Copperline

Everything on the record

Most AI works in private. Jori works in the open. Activity is the first page in the console, and every run, from a job or a mention, shows what triggered it, what they read, what they did, what they asked, and what it cost. Stop any run from wherever you can see it.

Activity

Task
Every Monday, read the Customer renewals table. For each row past its renewal date where Paid is No, post one reminder in @Slack #finance naming the owner and the amount, following /reminders. Then set Reminded to Yes on that row and finish with a one-line summary.
Schedule
Mondays at 08:00 Europe/Stockholm
Folder
Renewals
Tools3
Web search
Blocked
Outcome
Three reminders sent: Harbor House, Beacon Works, Larkspur Hotels. Rows updated.
Log
13 events
  1. Run started
  2. Model step completed
    in 4.2K · out 180 · total 4.4K · $0.01
    3s
  3. List table rows
    Customer renewals·4 rows
    0s
  4. Model step completed
    in 12K · out 1K · total 13K · $0.03
    5s
  5. Model step completed
    in 13.1K · out 260 · total 13.4K · $0.03
    3s
  6. Model step completed
    in 13.6K · out 90 · total 13.7K · $0.03
    2s
  7. Run completed

Showing 1–10 of 10 runs

Receipts, with the bill
Each run lists the model turns, the tokens, the tools, the seconds, and the dollars, at the rate the ledger charged.
Ask first means ask you
Set a tool to ask first and Jori requests before acting, with a code you can approve from the thread. Unattended runs can't touch an ask-first tool at all.
Stop means stop
Stop any run at any moment, and the record says who did.
How Jori handles access and data

The same Jori, wherever you work

Mention Jori in Slack, GitHub, or Linear and they answer in the thread. When the answer is a table, a store, or a file, it lands in the folder and the thread gets the link.

Each one modeled in depth, with its own tools and modes.

SlackLinearGitHubGmailGoogle CalendarNotionOutlook MailMicrosoft Calendar+ more
LinearCopperlineCOP

COP-73Tip-pooling certification

@jori what's left before this ships?

GitHubcopperline/payroll

Payroll sync test is flaky on CI#491

@jori can you fix this and open a PR?

Stored in your region

Choose an EU or US workspace. Jori stores your chats, files and workspace records in your chosen region.

Nothing shared between the two
Separate applications, databases and file storage in the EU and US.
What leaves the region
Some features use services that process data outside your chosen region, including web search, code execution and billing.

Opening to a few teams at a time.

Paid pilots, set up by us. Tell us what your team does by hand every week, and we'll be in touch if it's a fit.