on-device only

Your work log never leaves your laptop.

Chief tracks what is waiting on you, writes your work log as you go, and answers questions about your own week — on a model that runs on your machine.

Version 0.26.2 · no account, no telemetry

0 bytes to a server of ours
1 port on localhost
$0 per token, ever

what it does

Eight jobs it does for you, on your machine

Each one reads the tools you have connected, and each one says which source an answer came from. Connect one tool and you get the same shape of answer as someone who has connected all of them.

today

A morning brief that is already written

Open Chief and the day is there: your meetings, the reviews people are waiting on, the issues assigned to you. It is drawn from every tool you have connected, and a quiet day gets a short, plain brief rather than padding.

/brief

Works from: GitHub, Linear, Jira, Outlook, any calendar link

waiting on you

What is waiting on you, kept separate from what is yours

A review someone asked of you is a request. Your own open pull request is not. Chief lists them under separate headings so nothing urgent hides in a pile.

/waiting

Works from: GitHub

your pull requests

Why your pull request has not moved

For each of your open pull requests, Chief says what is holding it up: checks that failed, a review that has not come, comments still unresolved.

“What is holding up my pull requests?”

Works from: GitHub

standup

A standup you can read out as it is

What you finished since the last working day and what is still open, built from the work itself. On a Monday it looks back over the weekend.

“Draft my standup”

Works from: GitHub, Linear, Jira, Outlook

meetings

Prepared before you walk in

The next meetings, who is in them, and for a recurring one, what has happened since it last ran. Names come from a file you keep and confirm yourself, not a guess.

/prep

Works from: Outlook or a calendar link, plus GitHub

work items

Your tickets in one report

Everything assigned to you across GitHub, Jira and Linear, grouped as blocked, overdue, in progress and not started. Each line says what moved this week, what is blocking it, and whether it looks set to make its date, with the reason.

/items

Works from: GitHub, Jira, Linear

your team

For people who answer for a team

List the people or repositories you care about in a plain file. Chief shows what is waiting on review and what each person has open, and sheets for your one-to-ones. It reads only what your own GitHub access can already see.

/team   /1on1   /items team

Off until you list someone

work log

Ask about your own week

Merged pull requests are written into a log as they happen, in markdown you own. Ask what you shipped this week, last month, or what you should do first, and the answer shows how far back it looked.

/week   /log

Works from: GitHub, plus anything you add by hand

It would rather say nothing than make it up

Before a brief is saved, Chief checks it against what it was given. One that names a time, a number or a person that is not there is not kept. Where a read finds nothing, the answer says so without asking the model.

Fast on an ordinary laptop

Everyday questions are placed by meaning and Chief fetches the facts itself, so the small model has less to work out. It is one model, Gemma 4 E2B, on every machine. On Windows and Linux it runs on the processor unless you tick “Use graphics card”.

Yours to switch on

Drafts that ask a colleague for a review are off until you turn them on, and Chief never sends one. Keeping running in the tray and opening at login are both your choice.

connects to

The tools you already use

  • GitHub
  • Linear
  • Jira
  • Confluence
  • Outlook mail and calendar
  • Google, iCloud or Fastmail calendars

Chief only reads from these, with your own sign-in. Jira's sign-in asks for no write access at all. Slack and Teams are not supported yet.

why local matters here

Your work log is the most sensitive document you own.

It is every unshipped feature, every slipped date and every awkward thread, in one place. Chief keeps it in a SQLite file in your own app directory and asks a model on the same machine to read it. There is no account, no sync, and no vendor with a copy.

Read how it works
Your questions and answers never leave
Your work log database local file
Your notes and drafts markdown you own
Usage analytics none collected
Requests to your tools outbound, your token

Running in four minutes

01

Install the app

Builds for macOS, Windows and Linux. The llama.cpp engine is bundled, so there is no separate runtime to install and no installer account.

02

Download a model, once

First run fetches Gemma 4 E2B — about 3.8 GB, with a progress bar and a resumable download. After that it is yours offline.

1245 of 2019 MB

03

Connect one tool

GitHub first, via device code in your browser. The token is stored on this machine only.

B7C4-9QLD