tsk

A keyboard-only client for Strativ's ERP360 (Odoo 16), in the terminal. Seven screens, no browser and no mouse:

• Tasks — the tasks assigned to you, each expanding into its timesheet lines. Log, edit and delete hours; / takes a date — from the list it lists everything logged on that day across every task, inside a task it walks the cursor to the rows that match.
• Dashboard — hours logged per day this month against what was expected, and the ERP's own attendance clock: check in and out from the same screen.
• Time off — a year calendar of the days you took off, your leave balances, the public holidays, and a one-line form that files a request the way the web UI does.
• Employees — the office directory, a row per person; l opens one into their email, phone, department, team lead, project managers, time off approver, stack manager and the projects they are on. / filters on any of it. Read once, cached on disk, re-read with R.
• Meals — this month's meal bookings with the week's menu beside them; book today, tomorrow, the week ahead or a range, and cancel the same way.
• Requisitions — what you have asked the office for, as a table: category, the two dates, the stage in green, red or amber by what it means, and a tick where it was urgent. l opens a row into what its category asked for, and n files a new one — the fields come from the category you choose.
• Projects — the projects you are on, a row each: the name, the teams on it, and how many tasks it holds; a switches to every open project in the office. l opens one into its project manager and everyone on its teams, as a table of names and work emails. i filters the list, / asks where a person is and answers with the projects they are on. Cached on disk, re-read with R.

Written in Go with Bubble Tea. One self-contained binary, no C dependencies in the source.

Contents

• Features
• Installation
  • Download a binary (no Go required)
  • Build from source
• First run
  • Option A — a pass entry (recommended)
  • Option B — environment variables (no pass)
• Usage
  • Keymap
  • Typing hours and dates
  • The date jump
• Configuration
  • Custom keybindings
  • Environment variables
• How syncing works
• Files it touches
• Troubleshooting
• Development

Features

• All your tasks in one list. Pulled from ERP360, no hunting through the web UI.
• See the hours already logged. Open a task, its entries show up as a table.
• Log time in a few keystrokes. Date, what you did, hours — saved straight into ERP360.
• Fix mistakes. Change or delete any entry you logged, from the same screen.
• Typed hours are never lost. A failed save keeps them on screen and says so.
• Only your own hours. A colleague's time on the same task never counts as yours.
• "Where did Tuesday go?" One key lists a whole day across every task, with its total.
• A progress bar for today. How far through your 8 hours, updated as you type.
• A month at a glance. d opens a dashboard: hours logged per day, against what was expected, red/amber/green by how close to 8 hours, weekends and holidays labelled instead of drawn. < / > step to the previous or next month.
• The whole month's target, not just today's. logged 80:00 / 152:00, so a shortfall reads against what the month is billed for.
• Check in and out. c on the dashboard: a boxed button, green to check in, amber to check out, WFH/OFFICE and the running time beside it.
• Tell the ERP the month is done. C on the dashboard: a boxed Confirm hour logs beside the clock, a prompt naming the month, and every unconfirmed line of it is confirmed at once.
• A WFH request where the refusal happens. When the ERP turns a check in down for want of a work-from-home request, a one-line form opens under the button — two dates and a reason — and ✓ files it and tries the check in again.
• A year of time off on one screen. o opens a calendar of every day you took off, coloured by leave type, with public holidays and weekends dimmed and this month's caret where today is. Half days show as half-filled dates, requests still waiting on approval as underlined ones. Six months at a time — three a row, two rows — on a terminal 130 by 32 or bigger; taller ones spend the extra rows on air around the weeks.
• Your leave balances, from the ERP. Four boxes above the calendar — sick Time Off, 9, DAYS AVAILABLE — and each type's own initial filters the year down to it.
• Ask for time off without leaving the terminal. n opens a one-line form: leave type, full or half day, the dates, why. The days light up on the calendar as you type them, and ✓ files the request with the ERP after showing you exactly what it is about to send.
• This month's meals, booking and cancelling them. m opens a month grid with one bar per meal per day — amber breakfast, paprika lunch, green snacks — booked meals solid, open slots hueless, weekends and office holidays bare, and the week's menu pinned down the right. b books today, tomorrow, the week ahead or a range you type; c cancels the same way and the calendar shows the day as it will be; x clears one day whole. < / > step months.
• The office directory, in the terminal. e opens a row per colleague — name and job title in two columns — and l opens one into their email, phone, department, team lead, project managers, time off approver, stack manager and the projects they are on, as pills. / filters on any of that text; esc clears it. Read once, cached on disk, R re-reads.
• Your requisitions and where they stopped. r opens a table of everything you have asked the office for — category, submitted, deadline, stage, urgent — and l opens a row into what its own category asked: the purpose, the specification, the device it replaces, your note. The fields come from the ERP with their own labels, so a category nobody taught this app about still reads correctly.
• File one without the web UI. n opens a form under the table: pick a category and it becomes that category's own questions, one a line — a software name, a device to replace, a deadline, a box to tick — plus urgent and a note. ✓ shows you exactly what it is about to send.
• What you are working on, and who is on it with you. p lists the projects you are on — the ones you manage or whose teams you are in — with the teams and the task count, and a switches to all 89 the office has open. l opens a row into the project manager and a table of everyone on its teams with their work emails. i filters the list on the name, the teams, the manager and the people read so far; / asks where a person is and answers with a modal of the matching names grouped under their projects. Cached on disk, R re-reads.
• Never left wondering if it's working. A spinner marks every request in flight — reading tasks, logging hours, reading the month or the year.
• Find a task by typing. The list narrows as you go.
• No mouse, ever. ? lists the keys the current screen takes.
• Change any key, on every screen or just one. Rebind anything in a small text file; a [keys.meal] table changes a key on that screen alone.
• Your API key stays private. Encrypted at rest, never written to a file or a screen.
• Works with no internet. Everything is cached; entries reach the ERP when you are back.

Installation

Download a binary (no Go required)

One self-contained binary, nothing to install alongside it. Two platforms are built: Linux amd64 and macOS Apple Silicon (arm64). On anything else, build from source below.

Linux

curl -fL -o tsk https://github.com/strativ-dev/tsk-tui/releases/latest/download/tsk-linux-amd64
chmod +x tsk
mv tsk ~/go/bin/tsk        # anywhere on your PATH works
tsk

macOS (Apple Silicon)

curl -fL -o tsk https://github.com/strativ-dev/tsk-tui/releases/latest/download/tsk-darwin-arm64
chmod +x tsk
xattr -d com.apple.quarantine tsk    # Gatekeeper: the binary is not notarized
mv tsk /usr/local/bin/tsk            # anywhere on your PATH works
tsk

Without the xattr line macOS refuses to run it the first time — "cannot be opened because the developer cannot be verified" — since the binaries are not signed or notarized.

releases/latest/download/… always resolves to the newest release, so the same command upgrades an existing install. To pin a version, put the tag in the path instead: releases/download/v1.4.1/tsk-linux-amd64. Or take it off the releases page by hand.

The published Linux binary links the system libc (libc.so.6, libresolv.so.2), so it wants a glibc distro — on Alpine or anything musl-only, build from source with CGO_ENABLED=0, which produces a fully static binary.

Build from source

Go 1.22 or newer is the only hard requirement. Linux and macOS are the same commands; nothing in the build is platform-specific, and no C toolchain is needed.

git clone git@github.com:tasnim-strativ/tsk-tui.git
cd tsk-tui
go install ./cmd/tsk        # ~/go/bin/tsk

Or build in place:

go build -o tsk ./cmd/tsk
./tsk

Make sure ~/go/bin is on your PATH if you used go install.

Cross-compiling for another platform — say, a Linux machine building the Mac binary — is one environment variable, no C toolchain required:

env GOOS=darwin GOARCH=arm64 CGO_ENABLED=0 go build -o tsk-darwin-arm64 ./cmd/tsk

pass is what keeps your API key encrypted, and it is the recommended way to run this — see Option A. On macOS: brew install pass gnupg, plus brew install pinentry-mac so the GPG passphrase prompt has somewhere to appear. On Linux, your package manager has pass.

If you would rather not run a password store, Option B works without it.

First run

You need an Odoo API key and the database name. Generate the key in ERP360 under Preferences → Account Security → New API Key.

The database name is deliberately not in this repo — it is half of what someone needs to reach the ERP over JSON-RPC. Two ways to get it:

• Ask odoo baba on Slack.

• Read it from your own session: log in to erp360.strativ.se, open the browser console and run

  await fetch('/web/session/get_session_info', {
    method: 'POST',
    headers: {'Content-Type': 'application/json'},
    body: '{"jsonrpc":"2.0","method":"call","params":{}}'
  }).then(r => r.json()).then(d => d.result.db)

  The string it prints is the database name.

Now hand both to tsk, either way below. Pick one — each is complete on its own.

Option A — a pass entry (recommended)

Uses pass, the standard Unix password manager, so the key stays encrypted at rest and tsk can rotate it for you with K. Both values live in one entry, secret on the first line and the database below it, which is pass's own convention for metadata:

pass insert -m tsk/api-key

Type the two lines and end with ctrl+d. The entry should look like this — the API key first, on its own line, and the database on a db: line under it:

9f3c1a7e2b5d8406f1ae7c3b95d20e4867fa1cb2
db: example_erp_db

That is exactly what pass show tsk/api-key prints back. tsk reads line one as the key and looks for db: in the lines below it, so the order matters — a db: line on top would be read as your key.

(Both values above are made up — use your own key and the database name you looked up.)

Then run tsk. If the entry does not exist yet, it asks for the key on the first screen, saves it to pass, and fetches. esc at that prompt works offline on whatever is cached.

Option B — environment variables (no pass)

Nothing to install, nothing encrypted. tsk reads $TSK_API_KEY before it looks for a password store, so pass is never invoked at all.

Put the two values in your shell's config file, so they are there in every shell and you never type them again. Open the file for your shell in an editor and add:

fish — ~/.config/fish/config.fish

set -gx TSK_API_KEY 9f3c1a7e2b5d8406f1ae7c3b95d20e4867fa1cb2
set -gx TSK_ODOO_DB example_erp_db

zsh — ~/.zshrc · bash — ~/.bashrc

export TSK_API_KEY=9f3c1a7e2b5d8406f1ae7c3b95d20e4867fa1cb2
export TSK_ODOO_DB=example_erp_db

Both values above are made up — use your own key and the database name you looked up.

Then pick up the change and run it:

exec fish            # or: source ~/.zshrc — or just open a new terminal
tsk

Three things to know about this route, and why Option A is the recommended one:

• Edit the file, do not type the export at your prompt. A command line with the key in it lands in your shell history in plain text.
• The file is plaintext. Keep it to yourself — chmod 600 ~/.config/fish/config.fish (or ~/.zshrc) — and remember the key is then in the environment of every process that shell starts.
• K cannot rotate the key on this route, because saving goes through pass insert. Change the key by editing the same config file.

Either way

Without a database name — no db: line and no $TSK_ODOO_DB — the task list still loads, but timesheet lines cannot: the status line will say no Odoo database.

Usage

tsk starts on the task list. Press l to open a task, a to add an entry, enter to edit the row under the cursor, x to delete it, q to quit.

Press ? for the keys the current mode takes — the footer lists them, ? again puts them away. It is generated from the same bindings the app matches on, so it cannot drift from what the keys actually do.

Keymap

The defaults — see Custom keybindings to change them, and ? in the app for the keys the current screen takes.

Task list (where it starts)

Key	Does
j / k	next / previous task
g / G	first / last
ctrl+f / ctrl+b	half a screen down / up
l	expand the task, focus its rows
h	collapse
/	date jump — lists that day across every task
d o m e r p	dashboard / time off / meals / employees / requisitions / projects (2–7 too)
R	re-fetch tasks from the ERP
K	replace the stored API key
i	focus the search field
ctrl+u	clear the search and focus it
?	show or hide the key list
q	quit (asks first; ctrl+c quits at once)

Inside a task

Key	Does
j / k, g / G, ctrl+f / ctrl+b	move between rows
a	new entry at the top, dated today
enter	edit the focused row in place
x	delete the focused row (asks; y only)
/	jump to a date within this task
h	collapse and go back to the task line
esc	collapse and go back to the task line
i	collapse and focus the search field
ctrl+u	collapse, clear the search, focus it
q	quit (asks first; n returns to these rows)

Editing an entry

Key	Does
tab / shift+tab	date → description → hours → ✓ → ✕
enter	next field, or commit on ✓
ctrl+u	clear the current field
esc	cancel — at once when editing, after a prompt for a new entry

Search field

Key	Does
any key	filter by title and tag, live
esc / enter	back to the task list
ctrl+u	clear the query and collapse everything

Dashboard (d or 2)

Key	Does
g / G	start / end of the month
ctrl+f / ctrl+b	half a screen of days, down / up
< / >	previous / next month — > stops at the current one
c	check in, or check out (asks; y only)
C	confirm this month's hour logs (asks)
R	re-read the month from the ERP
t o m e r p	tasks / time off / meals / employees / requisitions / projects (1, 3–7 too)
i / ctrl+u	back to the tasks, in the search field
?	show or hide the key list
q	quit (asks first)

The WFH request line (opened by the ERP refusing a check in)

Key	Does
tab / shift+tab	the two dates → the reason → ✓ → ✕
enter	next field; on ✓ it files the request and checks in, on ✕ it closes the line
ctrl+u	clear the focused field
esc	close the line, nothing filed

Time off (o or 3)

Key	Does
j / k	next / previous month (l / h too)
ctrl+f / ctrl+b	a row of months down / up
g / G	January / December
enter	list this month's time off; esc closes
n	new time off request
s c a p	show only sick / casual / annual / paternity
esc	clear the filter (the same letter again does too)
R	re-read the year from the ERP
t d m e r p	tasks / dashboard / meals / employees / requisitions / projects (1, 2, 4–7 too)
i / ctrl+u	back to the tasks, in the search field
?	show or hide the key list
q	quit (asks first)

The time off request line (n)

Key	Does
tab / shift+tab	next / previous field
j / k / space	change the focused dropdown
s c a p	on the leave type, pick it outright
enter	next field; on ✓ it asks before filing, on ✕ it closes the line
ctrl+u	clear the focused field
esc	discard the request (asks first)

Meals (m or 4)

Key	Does
h / l	previous / next day
j / k	a week down / up
g / G	first / last day of the month
b	book meals — the line opens under the calendar
c	cancel meals — the same line, the opposite verb
x	clear this day, every meal on it (asks; y only)
< / >	previous / next month — > stops at the current one
R	re-read the month from the ERP
t d o e r p	tasks / dashboard / time off / employees / requisitions / projects (1–3, 5–7 too)
i / ctrl+u	back to the tasks, in the search field
?	show or hide the key list
q	quit (asks first)

The book / cancel meal line (b, c)

Key	Does
tab / shift+tab	scope → the two dates on a custom range → ✓ → ✕
j / k / space	today · tomorrow · week · custom
b l s	tick breakfast / lunch / snacks
enter	on ✓ it asks, then books or cancels; on ✕ it closes the line
ctrl+u	clear the focused date
esc	close the line, nothing filed

Employees (e or 5)

Key	Does
j / k	next / previous person
g / G	first / last
ctrl+f / ctrl+b	half a screen
l	open their details; h closes
/	filter the list — any key filters, enter keeps it
esc	clear the filter and collapse everything — from the prompt or the list
R	re-read the directory from the ERP
?	show or hide the key list
q	quit (asks first)

Requisitions (r or 6)

Key	Does
j / k	next / previous requisition
g / G	first / last
ctrl+f / ctrl+b	half a screen
l	open what its category asked for; h closes
n	file a new requisition — the form opens under the table
esc	close everything
R	re-read them from the ERP
?	show or hide the key list
q	quit (asks first)

The new-requisition line (n)

Key	Does
j / k / space	change the focused dropdown or tick the focused checkbox
tab / shift+tab	next / previous field
enter	next field; on ✓ it asks before filing, on ✕ it closes the line
ctrl+u	clear the focused field
esc	discard the line (asks first, once a category is chosen)

The fields are the category's own, so the form is empty until you pick one and changes when you pick another. It sits under the table, one field a line in the same boxed style as the time off form, with ✓ and ✕ lined up under the values.

Projects (p or 7)

Key	Does
j / k	next / previous project
g / G	first / last
ctrl+f / ctrl+b	half a screen
a	all projects / only yours
l	open its manager and its people; h closes
i	focus the search field — name, teams, manager, and the people read so far
/	find a person: a modal of the matching names, grouped by project (esc closes)
esc	clear the search and collapse everything
R	re-read them from the ERP
?	show or hide the key list
q	quit (asks first)

Read only, and it opens on your own — the ones you manage or whose teams you are in. The people are read once per project when you open it, cached with the list so a restart does not ask again, and the table is sorted by name; the manager is on screen straight away, since it comes with the list.

Confirm prompts

Key	Does
y	go ahead
n / esc	back out

Destructive prompts — quitting, deleting a line, cancelling meals — take y only, so a reflexive enter cannot fire them.

Typing hours and dates

Durations are read however you write them, and normalized when you leave the field:

7h30m → 7:30      7.5 → 7:30      90m → 1:30      7:30 → 7:30      7 → 7:00
:30 → 0:30        7: → 7:00

Dates fill in what you leave out, relative to the row you are editing (or today for a new entry):

8       → 08/08/26     (day only: keeps the month and year)
8/9     → 08/09/26     (day and month: keeps the year)
8/9/26  → 08/09/26

When you edit a row the date arrives selected — the first keystroke replaces it, tab keeps it.

The date jump

/ means two different things, because there are two different questions:

• From the task list — "where did that day go?" /12 resolves to the 12th of this month and opens a modal listing every entry logged on it, in any task, with the day's total. Nothing expands. esc closes it.
• Inside a task — "where is that row?" Here the date is matched part by part, so /12 finds the 12th of any month among that task's rows, /12/7 any 12th of July. The cursor moves to it; no modal covers the rows you are reading.

Either way the matching rows stay marked until you clear the jump (enter on an empty prompt, or ctrl+u).

Configuration

Custom keybindings

Every binding is a default, not a fact. Write the current keymap to the config file and edit what you like:

# Linux
mkdir -p ~/.config/tsk
tsk --print-keys > ~/.config/tsk/config.toml

# macOS
mkdir -p ~/Library/Application\ Support/tsk
tsk --print-keys > ~/Library/Application\ Support/tsk/config.toml

[keys]
half_down = ["ctrl+d"]          # back to vim's key
down      = ["j", "down", "n"]  # several keys per action
quit      = []                  # an empty list unbinds it; ctrl+c always quits

Any action can also be rebound on one screen only, with a [keys.<tab>] table — tasks, dash, time, meal, emp, req, proj:

[keys]
delete = ["x"]        # everywhere

[keys.meal]
delete = ["d"]        # ...but on the meal tab, d cancels the day's meals

A screen's own binding is matched before the tab keys, so the example above gives up d for the dashboard on the meal tab only. In the global table a key the tab bar owns is refused at startup instead, since the tab keys are matched first and the action could never fire.

Which actions a screen actually reads — anything else in its table is accepted and simply never fires there:

Screen	Actions it uses
[keys.tasks]	down up top bottom half_down half_up expand collapse jump edit add delete refresh set_key search clear_search clear_query focus next prev clear_field accept cancel quit
[keys.dash]	top bottom half_down half_up prev_month next_month clock confirm_hours refresh search clear_search quit — plus next prev clear_field accept cancel on the WFH request line
[keys.time]	collapse expand down up top bottom half_down half_up accept new_leave back refresh search clear_search quit — plus next prev cycle clear_field on the request line
[keys.meal]	collapse expand down up top bottom half_down half_up prev_month next_month book_meal drop_meal delete refresh search clear_search quit — plus next prev cycle clear_field accept cancel on the booking line
[keys.emp]	down up top bottom half_down half_up expand collapse jump back refresh quit — plus focus and cancel on the filter prompt
[keys.req]	down up top bottom half_down half_up expand collapse back new_leave refresh quit — plus next prev cycle clear_field accept cancel on the new-requisition line
[keys.proj]	down up top bottom half_down half_up expand collapse mine search jump back refresh quit — plus focus and cancel in the query field and the find prompt

help (?), the seven tab keys (tasks_tab dash_tab time_tab meal_tab emp_tab req_tab proj_tab) and the confirm keys (yes yes_only no) work on every screen, so they belong in the global [keys] table rather than in one screen's.

Keep only the lines you want to change — anything absent keeps its default, and no config file at all is perfectly fine. Action names are listed by --print-keys. Keys are spelled the way Bubble Tea spells them: a single character, a ctrl+ / alt+ / shift+ compound, or one of enter esc tab shift+tab space backspace delete up down left right home end pgup pgdown.

A misspelled key or an unknown action stops the program with a message rather than starting up with a keymap that silently does nothing.

The footer follows a rebind on its own, since help and behavior read the same bindings.

Environment variables

Variable	Default	Purpose
TSK_API_KEY	—	use this key and skip pass entirely
TSK_PASS_NAME	tsk/api-key	which pass entry holds the key
TSK_ODOO_DB	—	Odoo database, overriding the db: line in pass
TSK_API_URL	https://erp360.strativ.se	point at staging or a local Odoo
XDG_CONFIG_HOME	~/.config on Linux, ~/Library/Application Support on macOS	where the config and cache live

How syncing works

The REST API and JSON-RPC each cover part of the job:

Call	Used for
GET /api/v1/tasks/my	your task list
GET /api/v1/timesheets/hour-log-summary	today's total, for the progress bar
POST /api/v1/timesheets/log	creating one entry
JSON-RPC account.analytic.line search_read	reading a task's lines
JSON-RPC write / unlink	editing and deleting a line
JSON-RPC get_employee_hour_logs	the dashboard's month of daily hours
JSON-RPC hr.employee / hr.attendance	checking in and out, and the session you are in
JSON-RPC serp.meal.booking / serp.meal.type	the month's meals, booking and cancelling them, and the days nothing is served
JSON-RPC serp.meal.menu	what is on the menu that week
JSON-RPC hr.leave / hr.leave.type	time off: the year's requests, the balances, filing one
JSON-RPC serp_attendance.wfh_request	filing a work-from-home request when a check in is refused
JSON-RPC confirm_hour_logs	telling the ERP a month's hour logs are done
JSON-RPC hr.employee.public	the office directory, and one person's own detail
JSON-RPC serp.general.requisition	your requisitions, their stage, the properties each category asked for, and filing one
JSON-RPC project.project + serp_project.team	the open projects, their manager, their teams and their task counts
JSON-RPC res.users	the names and work emails of the people on a project's teams
JSON-RPC serp.general.requisition.category	the categories you can file under, and the fields each one asks

Worth knowing:

• Lines are read lazily. Expanding a task reads it once; R clears that so open tasks are read again.
• A read merges, it never replaces. Entries you typed but the ERP has not confirmed are kept, and app-created rows carry negative ids so they cannot collide with an Odoo line.
• Reads are filtered to you. Odoo's own task form lists every employee's lines; this does not.
• Nothing retries by itself. One entry per request, and a timed-out retry could double-log, so a failure is reported and left for you to decide.
• The API key lives in memory, the Authorization header, and nowhere else. Not in a URL, not in a log line, not in an error message, not in the cache file.

Files it touches

Its own directory, plus the pass entry if you chose Option A:

Platform	Directory
Linux	~/.config/tsk/
macOS	~/Library/Application Support/tsk/

$XDG_CONFIG_HOME overrides that on either platform, so set -x XDG_CONFIG_HOME ~/.config on a Mac puts everything in ~/.config/tsk/ instead.

File	What
tasks.json	cached tasks and hours, so it works offline
employees.json	the office directory, read once and shown from here
projects.json	the open projects, their teams and their managers, same idea
config.toml	your keybindings (optional)
pass entry tsk/api-key	API key on line one, db: below it (Option A only)

tasks.json holds real hours and task names, and employees.json and projects.json your colleagues' work emails and phone numbers — all three worth keeping out of any repo or paste.

Troubleshooting

no Odoo database — add a db: line to the pass entry Timesheet lines come from JSON-RPC, which needs the database name. pass edit tsk/api-key and add db: <database-name> as the second line, or export TSK_ODOO_DB.

pass not found — install password-store, or export TSK_API_KEY You are on the pass route without pass. Either install it — brew install pass gnupg on macOS, your package manager on Linux — and initialise a store (pass init <gpg-id>), or switch to Option B and set TSK_API_KEY.

A GPG passphrase prompt appears Expected — pass show runs with the terminal handed over to it, so a tty pinentry works without corrupting the screen. gpg-agent caches it after the first time.

offline — showing the tasks on disk The ERP could not be reached. Everything still works against the cache, and hours you type are kept locally until a write succeeds.

A task shows no entries even though Odoo has some The first read failed (usually the missing database name). Collapse and expand it to try again; failures are not remembered as "already read".

401 / the key prompt opens by itself The key was rejected or revoked. K stores a new one.

ctrl+f or ctrl+u seems to be swallowed Your terminal multiplexer or shell may claim it first. ctrl+l was dropped as a binding for exactly this reason. Rebind anything that clashes — see Custom keybindings.

Development

cmd/tsk/         entry point
internal/model/  root model, one Update handler per mode, View
internal/parse/  hours and dates — pure, table-tested
internal/store/  the cache on disk, and the key from pass
internal/api/    REST client and Odoo JSON-RPC
internal/config/ the config.toml keymap, and where it lives per platform
internal/theme/  every color and style, in one place

go test ./... && go vet ./...      # the gate before any change is done

Conventions worth keeping: no I/O in Update or View (disk and network go through a tea.Cmd), minutes are stored as minutes and formatted only when rendered, totals and the progress bar are derived on every render rather than cached, and every parsing rule has a table-driven test. The rendering tests assert real terminal widths — a line wider than the screen wraps and pushes the layout out of place. CLAUDE.md carries the longer reasoning behind these decisions.