@jori works in Slack, GitHub, and Linear
Hand over the work you repeat.
The release checklist. The dependency sweep. The Thursday triage. Jori runs them where the work already lives, and leaves behind a live app your team opens instead of a message that scrolls away.
Copperline 2.14Cuts Thursday
2blocking1in review11ready
Needs a person
COP-73Tip-pooling certificationJonas
Review docs came back with two signatures missing.
#491Payroll sync test is flakyUnowned
Failed twice on CI this week. Nobody assigned.
Jori rechecks every morning and before the cut. Everyone opens the same page.
It learns how your company works
Jori reads what is already happening across your tools and works out the bodies of work your team would name out loud. That is what the apps are built on, and it sharpens the longer Jori runs.
- Assembled from activity
- No wiki, and nothing anyone has to keep updated. Jori reads the threads, issues, and pull requests that already exist.
- Grouped the way people talk
- Single threads of work roll up into the efforts a team actually names: a release, a compliance push, a customer escalation.
- Sharper the longer it runs
- Every run adds to what Jori knows about your company. This is the part a new tool cannot copy on the day you switch.
2.14 release14 threads · 4m
Tip-pooling compliance6 threads · 1h
Harbor House escalation3 threads · 22mAssembled from activity. Nothing here was typed in.
When the work repeats, it gets an app
Describe what your team keeps doing by hand. Jori works out what it needs, builds the app, and puts it in front of everyone.
- It holds real state
- Not a saved summary. What is blocking, who owns it, and what changed since yesterday.
- One page, not one per person
- Everyone opens the same one, holding the same state. Send it outside the company with a link that expires when you say so.
- A run keeps it current
- Jori rechecks on a schedule, or when something moves in a connected tool. Open it tomorrow and it already knows.
Modelled in depth, not just connected.
Gmail
Google Calendar
Outlook Mail
Microsoft Calendar#engCopperlineMaya Lund09:12
JoriAPP09:12
JoriAPP09:18
The rest, you just ask for
Mention Jori in Slack, GitHub, or Linear and it does the one-off job right there in the thread.
CopperlineCOPCOP-73Tip-pooling certification
@jori what's left before this ships?
copperline/payrollPayroll sync test is flaky on CI#491
@jori can you fix this and open a PR?
It works on your terms
Handing over real work means handing over real access. Jori is built so you never have to take its word for anything.
- Permission modes
- Every action Jori can take has a mode: allowed, ask first, or blocked. Posting, commenting, changing: you decide which need your sign-off.
- Ask-first approvals
- Set a tool to ask first and Jori requests before acting, with a code you can approve right from the thread. Denied requests never run.
- Receipts for every run
- Every run records what Jori read, what it did, and what it asked. Open any run in the console and check.
Search issues and PRs
Search issues and pull requests on GitHub.
Add comment
Comment on a Linear issue.
Create pull request
Create a GitHub pull request.
Search web
Search the public web.
Comment on the certification issue
- On: COP-73 · Tip-pooling certification
- Asking Jonas which two signatures are missing
- Posted as you
Opening to a few teams at a time.
Tell us what your team keeps doing by hand. We're setting up the first teams ourselves, so the fit matters more than the queue.