Harbor CLI
Harbor in the terminal: a full-screen app with your whole harbor, and commands for scripts and agents.
npm install -g @harborppm/cli
harbor # the full-screen app (signs you in the first time)
harbor mine # or one command at a time
Needs Node 22 or later.
New to Harbor?
You can start from the terminal. A harbor of your own is free for 30 days, no card; after that it's $49 a month for the whole crew, not per seat.
npm install -g @harborppm/cli
harbor signup # make your account in the browser (email or Google), then come back
harbor # name your harbor and its first project, and you're in
harbor signup opens Harbor's page on Create; confirm your email from the letter it sends when you get a moment. The first time you run harbor with no harbor yet, it asks for a name (Enter takes a suggestion) and, if you like, a first project, then opens on it. Joining a team's harbor instead? Open the invite they sent you, and harbor opens on their harbor.
The full-screen app
harbor on its own takes over the terminal, like htop or lazygit, and gives it back when you press q. It opens on Harbor's mark (the teal tile, the H and three boats, drawn in half blocks) while your harbor loads; after that the sidebar holds just the screens. Then:
- Today: today's focus (
fadds or takes off the task you're on, up to three) and your check-in (c); what's on you, late first; who's waiting on you; your risks and issues. - Inbox: the same pings as the website: waiting on you, sign-offs, mentions. Enter opens one; it's marked read.
- Projects: every portfolio, program and project with its health. A project opens on its board (columns side by side;
fandpshow only someone's cards or one priority), its list, or its budget and spend ledger (v); space picks the card or row you're on, andmmoves, assigns, dates, pushes a week, sets the priority of or finishes everything picked at once (uputs them all back);echanges its details: lead, dates, budget, health by hand with a note.Pruns its pre-mortem: everyone answers "it failed; what happened?" alone for five minutes, then each answer becomes a risk (r), folds into one already raised (m) or is left out (l). - Programs: the review: programs worst first, with their lead, end date, late work and where they sit on the priority matrix;
mwrites a next move,hsets a health by hand (with why) or hands it back to the late work,oandpshow someone's or one portfolio's. A program shows its projects and milestones side by side (madds a milestone, space ticks one), its next move and health;vreads it project by project, each with its bar across the months, open tasks by status and worst risks. A portfolio opens as a board (programs, with risks, next milestones and money beside them);vreads it program by program.eon a program also names what's holding it back, what it waits on, its impact and its baseline, with its health history below, andrreads its status report. A milestone can wait on projects and need someone's sign-off (they approve it or ask for changes). A project's details set its plan by month and what it waits on; a portfolio's set the priority matrix's rules.:then "new portfolio" makes one. - Risks: the register, worst first;
t,oandpnarrow it by kind, owner or portfolio,aadds closed ones,hdraws the heat map over it andcnarrows it to one of its cells. Enter changes one with every field the website has (status, owner, likelihood, impact, mitigation, contingency, resolution, rationale, notes, updates);nlogs a risk, issue or decision. - People: open and late work and the next four weeks against each person's capacity; Enter changes their capacity, role, or the time they're promised to a program.
- Roadmap: a portfolio's programs and projects across the months, in their health's colour, ◆ for milestones.
- History: who changed what, for a portfolio, program or project (
spicks which). - Calendar: the month with each day's tasks and milestones; arrows move the day,
[]the month, Enter goes into the day's tasks. - Brief (
0): the weekly brief the website writes, for all portfolios or one (p), with how many programs sit at each health and the notes that opened;fswaps in the shipping forecast andycopies what's shown (in a terminal that lets apps copy; tmux needsset-clipboard on). - Crew (
C): who's aboard and what each can do. The owner switches someone between editing and viewing (Enter), invites by email (i), copies (y) or withdraws (w) a letter still out, makes a read-only share link to a portfolio (s) and picks who gets its Monday update (m), and makes a project's intake form (f). Everyone sees the apps they connected (ddisconnects one), turns their emails on or off, and opens Keep in the browser. - Goals (
G): each portfolio's goals with how far along they are, off track in red, and their key results. Enter folds a goal open to read why it matters, what each key result counts and who last moved its number, and folds it shut again; it changes nothing, so a viewer can read too.nsets a goal;eon a goal renames it, gives it an owner, a due day or why it matters, adds a number key result or counts a program or project toward it;eon a number key result moves it;dremoves the goal or key result. - Reports (
O): the Reports page's dashboards, each chart drawn as bars with its numbers.nmakes a dashboard (the first starts with a few charts),aadds a chart (what it counts, then how it's split), Enter renames a dashboard or chart, splits a chart another way or moves it,[]move one,dremoves it.
: also opens three pages that aren't screens of their own. Recently deleted lists what was deleted in the last 30 days, and Enter brings one back (for editors; it says first when what it sat in is gone too). Sheet links lists yours, n makes one for a program (or, for the owner, the whole harbor) and copies it, since it shows only once, and d turns one off. API keys lists yours with when each was last used, and d revokes one; n opens the website, where a new key is made and shown once.
A task changes in place too: title, status, owner, due date (2026-10-14, today, +3), priority, project, what it waits on (type a key or words), how it repeats, notes, checklist steps, comments (C changes or takes out one of yours). s adds a subtask under it and T saves it as one of its project's templates. On a project, T starts a task from a template and M opens its Messages: one conversation for the whole project, where n writes, a answers the message in the cursor (the answer sits under it), e changes yours and d deletes. M on a program opens the program's Messages the same way.
Keys: ↑↓ (or j k) and ←→ (or h l) move, Enter opens, Esc goes back, : finds anything (a screen, "new project", a project or program by name), / finds a task by its key or words, n makes something new, e changes what's open, [ ] move a card a column, x marks it done, d deletes (it asks first), u undoes your last change, H switches harbor, ? lists them all.
It runs on the same engine as the website: health, task keys, limits and undo work the same way, changes save as you go (the header says when, and holds them while you're offline), and changes anyone makes on the website or elsewhere show up within a couple of seconds. It needs full access, which harbor login asks for by name; an older sign-in is asked again the first time.
It has colours for dark terminals and for light ones, and picks by asking the terminal for its background (or reading COLORFGBG); a terminal that doesn't say gets the dark ones. harbor theme light or harbor theme dark settles it, harbor theme auto goes back to asking, and HARBOR_THEME overrides it for one run.
harbor help starts with the dozen commands most people need; harbor help all lists every one. It shows the mark too, in a terminal with colour; piped, or with NO_COLOR set, it's plain text. harbor --version says which version you have.
On the website
Your harbor is the same one at harborppm.com, signed in with the same account, so the people you work with don't need a terminal. The website adds what a team shares:
- Your crew: invite people by email under People; they see the same boards, risks and roadmap, and their changes reach your terminal within seconds.
- Status for others: the weekly brief, a one-click status report, and read-only links for stakeholders.
- Intake forms: a public form that drops requests onto a project's board.
- GitHub: a pull request that names a task's key (RR-42) shows on the task and moves it along.
- Claude and other AI apps, connected over MCP from harborppm.com/ai.
harbor open RR-42 opens a task on the website (in the right harbor, even when the browser had another one open), harbor open Ridge a project, and harbor open on its own opens Today. harbor invite [email protected] sends Sam the same invite letter the People page does (--viewer to let them look but not change anything); only a harbor's owner can invite. harbor calendar prints your private calendar link, to add to Google, Apple or Outlook calendar: your due dates, milestones and sign-offs beside your meetings, kept up to date (--program NAME for everything dated in one program, --new to swap the link for a fresh one, --off to turn it off). harbor roadmap "Next steps" says whether a project is a public roadmap page and prints its link; --publish publishes it (Now, Next and Shipped, task titles only, on a link that can't be guessed, which stays the same while it's live), --publish --dates adds the day each thing shipped (titles only is the default), and --off takes it down at once. Only a harbor's owner can publish. harbor projects --json gives each project's public and url.
The website has the commands too: turn on Command line at the bottom in your menu, press /, and type mine, add "Call the mill" #ridge @sam --due fri or done RR-12.
Your plan in your repository
harbor init in a code project writes a .harbor/ folder at the top of the repository: one plain file per task in a project, with its title, status, owner, due date, priority and what it waits on, and its notes below. Edit them by hand, review them in pull requests, keep them in git like any code.
harbor init "Cedar site" # or its key: harbor init CS
$EDITOR .harbor/tasks/CS-4.md # status: doing, owner: Sam, due: 2026-11-07…
harbor sync # sends the edits, brings the website's back
---
title: Move checkout to the new API
status: doing
owner: Sam Rivera
due: 2026-11-07
priority: high
waits: [CS-2]
---
Old endpoints go away on Nov 20.
A new file with any name is a new task: harbor sync adds it and renames it to its key. A field changed in a file and not on the website goes to Harbor; one changed in both places keeps the website's and says so. Removing a file doesn't delete the task (mark it done instead). On a fresh clone, run harbor sync before editing. harbor init --hook adds a git post-commit hook that syncs after each commit, and --dry-run on either says what it would do without writing or sending anything.
No account? harbor init --local makes a plan that lives only in the folder (the rest of it in .harbor/plan.json), and harbor in that folder opens it full screen, offline and free. Later, harbor init PROJECT moves its tasks into a project on harborppm.com.
In your shell prompt
harbor prompt prints a few characters for your prompt: ⚓ 2 today · 1 late, with late work in coral, and nothing at all when you're clear. It never waits on the network: it shows the counts it kept and fetches new ones in the background when they're more than five minutes old, or after you change a task. harbor prompt --init zsh (or bash, fish, starship) prints the lines to add to your shell's setup, so harbor prompt --init starship >> ~/.config/starship.toml does it in one go:
# ~/.zshrc
setopt prompt_subst
RPROMPT='$(harbor prompt --shell zsh)'
Staying up to date
npm doesn't update a global install by itself, so once a day harbor asks npm whether a newer version is out, alongside whatever command you ran, and says so in one line when there is (npm install -g @harborppm/cli@latest --prefer-online updates it). It says nothing in scripts, pipes or CI; set HARBOR_NO_UPDATE_CHECK=1 (or NO_UPDATE_NOTIFIER=1) to turn it off.
Text from others
Task titles, names and notes can come from an intake form, a GitHub pull request or anyone in a harbor. Before the commands or the app show them, harbor takes out the control characters a terminal would act on (escape sequences, backspaces, text-direction overrides), so a title can't set your clipboard, retitle the window or hide what's around it. --json keeps the data exact, with those characters written as \u escapes.
Signing in
harbor signup is for a first visit: the same sign-in, with the page opened on making an account. harbor login registers the CLI with Harbor and opens the same page Claude and other apps use: it names "Harbor CLI" and asks what to allow. Choose Allow reading only (or run harbor login --read-only) if it shouldn't change anything. The sign-in is saved in ~/.config/harbor/credentials.json, readable only by you, and refreshes itself for 30 days.
harbor logout forgets it on this machine. To end its access everywhere, disconnect Harbor CLI under Connected apps in Harbor's menu.
Commands
harbor harbors the harbors you belong to
harbor whoami who you're signed in as, where, and which
build of the site answers
harbor use HARBOR|none the harbor to work in when you're in several
harbor programs programs and their projects
harbor projects [words] [--program P] projects with health and open work
harbor forecast [PROJECT] [--program P] when projects will likely finish, from
how fast their crews finish tasks
harbor try PROJECT --drop RL-4 --borrow Sam=3
dry dock: the forecast with changes tried
on a copy (--apply makes them, --save keeps
them to show someone; harbor help try)
harbor why PROJECT|TASK|MILESTONE what's holding it up: the line of task
waits that sets its date, slack per link
harbor barnacles PROJECT work added since the plan was set: by
week, by who, and the slip it explains
harbor baseline PROJECT [--set|--reset] reads a project's baseline; --set commits
its dates now (--dry-run says what)
harbor hill [--program P] where each project is on its hill
harbor hill PROJECT --at 0-100|top|done move it: up to 50 is figuring it out,
past 50 is getting it done
harbor mine what's on you, late first, and the tasks
others own that you're also on
harbor catchup [--since DATE] while you were away: handed to you,
decided without you, what moved
harbor clock [NAME] [--zone ZONE|here|none] [--hours 9-17]
who's working now; set your (or NAME's) time zone and hours
harbor tasks [words] [--project P] [--assignee me|none|NAME] [--late] [--status S,S] [--all]
harbor show TASK one task in full: who's on it, its files, its
web link and the date its owner's queue suggests
(pilotDue in --json)
harbor files PROJECT [--kind image|doc|link]
every file on a project's tasks, newest first,
with the task each is on
harbor open [TASK|PROJECT] open it on the website (or Today)
harbor invite EMAIL [--viewer] invite someone to your harbor by email
harbor calendar [--program P] [--new|--off] your private calendar link (.ics)
harbor roadmap PROJECT [--publish] [--off] a project's public roadmap: read, publish or take it down
harbor shore PROGRAM [--url URL] [--on forecast,health,notes] [--off KINDS] [--test] [--remove]
a program's Slack, Discord or Teams channel: the morning
forecast, health changes and notes for later post there
harbor program "NAME" [--portfolio P] [--lead me|NAME] [--starts DATE]
[--ends DATE]
harbor project "NAME" --program P [--lead me|NAME] [--starts DATE]
[--ends DATE] [--budget N] [--from "DONE PROJECT"]
--from: dead reckoning, its tasks due when
they really finished in that project
harbor add "TITLE" --project P [--assignee me|NAME] [--also "NAME, NAME"] [--due DATE|pilot]
[--priority low|medium|high|urgent] [--status S] [--comment TEXT]
[--starts DATE] [--over-limit] [--literal] [--dry-run] [--unless-exists]
no TITLE: one title a line from stdin
--due pilot takes the earliest day the owner's queue
suggests (their open work due first, weekly pace, time
away, what it waits on, how long their similar tasks
took); it needs an owner, and an empty queue gives
their next working day. A date that won't hold says so
harbor start TASK | submit TASK | done TASK [--confirm] [--over-limit]
harbor edit TASK [--title T] [--assignee me|none|NAME] [--also "NAME, NAME"|none]
[--due DATE|pilot|none] [--starts DATE|none]
[--priority P] [--status S] [--notes TEXT]
[--repeat weekly|biweekly|monthly|never]
[--waits-on TASK,TASK|none] [--confirm] [--over-limit]
harbor comment TASK "TEXT"
harbor checkin "WHAT YOU'RE DOING" [--on-blocker]
harbor risk "TITLE" --project P|--program P [--impact 1-5] [--probability 1-5]
[--owner NAME] [--due DATE]
harbor issue "TITLE" --project P|--program P [--impact 1-5] [--owner NAME]
[--due DATE]
harbor decision "TITLE" --project P|--program P [--owner NAME] [--due DATE]
[--turned-down T] [--look-again DATE] [--supersedes "OLD"]
harbor risks [words] [--kind risk,issue,decision] [--project P] [--closed]
harbor raid "TITLE" [--status S] [--owner me|none|NAME] [--impact 1-5] [--probability 1-5]
[--due DATE|none] [--update TEXT] [--mitigation T] [--resolution T]
[--turned-down T] [--look-again DATE|none] …
one risk, issue or decision in full, or change it
harbor review [WORDS] [--mine|--owner NAME] [--portfolio P] [--done]
the review: programs worst first, with next moves
(reads only; harbor submit moves a task to In review)
harbor thanks [TASK "LINE"] [--to NAME] a one-line thanks for a task (--milestone, --decision);
on its own, the thanks you were given in the last 30 days
harbor bridge run the review as a meeting: one project a screen,
what changed since the last one, log decisions,
actions and risks live, post the summary to chat
harbor bridge --list [--program P] what changed since each program's last review, every
item, as text (--json for agents); doesn't hold the meeting
harbor next-move PROGRAM "TEXT" write a program's next move
harbor health --program P|--project P|--portfolio P STATE [--note WHY]
set its health by hand (auto hands it back)
harbor brief [--portfolio P] [--all] [--say] the weekly brief (--all: every late and done task)
harbor report PROGRAM a program's status report, as Markdown
harbor export tasks PROJECT|risks|review [--all]
a spreadsheet (CSV) to stdout
harbor import FILE [--project P] [--portfolio P] [--no-people]
add tasks from a CSV file
harbor draft "WORDS" --project P|--program P|--portfolio P|--new program|portfolio [--add]
Harbor's AI drafts tasks, projects or programs
harbor draft add add the draft shown last
harbor premortem PROJECT ["WHAT WENT WRONG"] [--start]
harbor voyage PROJECT ["YOUR LINE"]
harbor messages PROJECT ["TEXT"] [--limit N] | messages PROJECT --edit "TEXT" [--message ID]
harbor chat TASK|PROJECT|PROGRAM ["TEXT"] [--reply N] [--watch]
harbor chat @NAME [@NAME…] ["TEXT"] [--watch]
harbor chats
harbor note PROJECT ["NOTE"] [--opens DATE|--milestone NAME|--off-track]
harbor sound TASK [--answer DAYS|--ask NAMES|--settle DAYS] [--why TEXT]
harbor soundings [PROJECT]
harbor goals [PORTFOLIO] each portfolio's goals, off track first
harbor goal "GOAL" [--title T] [--owner NAME] [--due DATE|none] [--link WORK] [--unlink WORK]
[--kr "KR" --at N|--target N [--start N] [--unit U]|--counts WORK]
harbor goal "TITLE" --new [--portfolio P] [--owner NAME] [--due DATE] [--why T]
harbor milestones [PROGRAM] [--project P] [--done]
harbor milestone "NAME" [--program P] [--due DATE] [--rename T] [--reached|--open]
[--signs-off NAME|none] [--approve|--changes NOTE]
harbor milestone "NAME" --new --program P --due DATE
harbor reports [DASHBOARD] the Reports page's dashboards, each chart as numbers
harbor ashore [--weeks N] [--country CODES|none] [--person NAME]
harbor limit PROJECT [COLUMN N|none]
harbor week [--next|--last|--week DATE] [--review]
harbor week TASK --day DAY [--hours N] | week TASK --off [--day DAY] | week --day-hours N
harbor init [PROJECT] [--hook] [--dry-run] a project's tasks as files in this repository
harbor init --local [NAME] a plan in this folder alone, no account
harbor sync [--quiet] [--dry-run] the files and the website, in step both ways
harbor handover PERSON [--to NAME] [--until DATE] [--note TEXT] [--keep ID,ID] [--confirm]
harbor handback PERSON
harbor fog [--project P] tasks nobody has touched for three weeks, longest first
harbor fog --sweep [--project P] the same, one at a time: still needed, a new date, or drop it
harbor fog keep TASK it's still needed: out of the fog
harbor watch [--project P] [--bell] a live ticker of the harbor's changes
harbor watch --once [--since TIME] [--json] the latest changes (or all since TIME), once, for scripts
harbor lifeboats [--program P] work only one person knows, each with a second pair of hands
harbor lifeboats N [--person NAME] adds that second pair of hands
harbor follow TASK|"RISK" --person NAME someone follows it too
harbor convoys [PROGRAM] promises between programs, and how each stands
harbor convoy ask PROGRAM --to OTHER --by DATE "WHAT"
harbor convoy accept|decline|deliver|undeliver|move|withdraw CONVOY [--project P] [--note WHY] [--by DATE]
harbor salts PROJECT [--risk N|--task N|--put-away N] what finished projects like it ran into
harbor rank PORTFOLIO [--order "A, B, C"|--clear] which ship docks first
harbor agent [--agent NAME]
harbor agent report TASK "WHAT YOU DID" [--start] [--agent NAME]
harbor handover Priya lists everything Priya carries (open tasks, sign-offs waiting on her, risks and issues she owns, projects and programs she leads) and who should take each, from who has room this week. Nothing moves until you add --confirm. --until DATE is for time away: Priya shows as away on People, and harbor handback Priya gives back whatever is still with whoever took it. --note goes with each task and risk as a comment.
harbor fog lists the open tasks nobody has opened, moved, edited or commented on for three weeks, longest first. harbor fog --sweep walks through them one at a time in a terminal: k still needed (clears the fog), d a new date, x drop it, s skip, q stop. On the board, in the app and on the website, those cards show dimmed.
harbor watch turns a narrow split or a tmux pane into a live ticker of your harbor: cards moving, comments, health changes, a line each as they happen, over the same live updates the website uses. Lines about your own work (your tasks, mentions of you, what you lead) are bright and the rest dim; --bell rings the terminal's bell when something of yours changes, and --project keeps to one project. It starts with the latest few changes and the time it began listening; --since 14:30 (or a date) starts from then instead, on this computer's clock (14:30Z or 14:30 UTC for UTC); the header names the time zone the ticker's times are in, and Harbor says "Nothing since 14:30 BST." when nothing has. A change the GitHub link made reads "Finished RR-4 … via GitHub", as History does. q stops; piped or with --json (one JSON object a line) it runs until it's killed, and --once prints what's there and returns, for scripts. Harbor keeps the latest 40 changes, so a --since further back says where its list starts.
harbor convoys lists the promises between programs: one program's ask of another for a thing by a day, and how it stands (waiting for an answer, in time, late on the delivering project's forecast, declined, delivered); harbor convoys Footwear splits one program's into what it waits on and what others wait on it for. harbor convoy ask "Member App" --to Footwear --by 2026-12-15 "Shoe photos" asks; the asked side answers with harbor convoy accept "shoe photos" --project "Ridge Runner", decline … --note WHY or deliver, and the asking side can move … --by DATE or withdraw. A convoy is named by its words; when they fit two, Harbor lists both.
harbor salts "Ridge Runner" shows up to three old salts: what finished projects like it ran into (risks that came true, issues, voyage log lines, tasks that finished long late), with what helped. --risk 1 puts the first on the register, --task 1 adds it as a task, --put-away 1 stops showing it. harbor rank "Summit Line" shows the order a portfolio's projects dock in, who set it and how the newest ranking link stands; --order "Daypack, Ridge Runner" sets one (open projects of that portfolio, first to dock first) and --clear takes it off. The ranking link the crew answers in pairs is made on the portfolio page.
harbor lifeboats lists the work only one person has touched (a project, their corner of one, a task others wait on, their serious risks), numbered, each with someone who has room this week and already works nearby. harbor lifeboats 2 puts that person on line 2 as a second pair of hands (--person NAME for someone else); harbor follow RR-4 --person Sam does it for one task. Following doesn't take the work over. harbor raid "DECISION" --still-stands "WHY" says a decision that came back for a look still stands.
Agents on the crew: put an AI app on People with Add an agent and assign it tasks like anyone else. An agent working through the CLI (Claude Code, say) runs harbor agent for its tasks, in progress first, with their notes, checklists and latest comments. When it's done, harbor agent report RR-4 "Drafted 12 questions; two need Dana" adds its note as the agent's comment and moves the task to In review and asks whoever gave it the task to check it. They approve it, or send it back with a note, which harbor agent shows first. An agent never marks its own work Done.
harbor week is your own week, and only you see it: Monday to Friday with the tasks you put on each day, the hours each should take against the hours you work (--day-hours 8; 7 unless you say), a warning on a day that's too full, and your open tasks not on a day yet (ones in review wait on someone else, so they're left out). harbor week RR-42 --day wed --hours 3 puts a task on Wednesday (--next for next week), harbor week RR-42 --off takes it off the week, and from Friday (or with --review) it says what you planned against what you finished. The website's Your week is the same plan, with drag and drop.
A task has one owner (--assignee), who answers for it and whose load it counts against, and anyone else on it with them (--also "Sam, Aya"): they see it under Also on in harbor mine and on Today, and count as knowing it. harbor edit RR-4 --also none leaves only the owner.
harbor add --project Trail --comment "From Monday's call" < list.txt adds one task per line of the file, each with the comment (every option applies to every line); --dry-run asks Harbor to add them on a copy it throws away, so it shows each task as it would really be (key, column, owner, priority, dates, parent, milestone), an open task that already has the title, and anything it would refuse and why; it exits 1 when something would be refused. The key it shows is a forecast, not held: an add from anyone in between takes it. --unless-exists adds a title only if the project has no open task by that name (done tasks aren't checked, so a weekly chore still goes in), so a retried script doesn't double up. --json has the dry run's shape, so a script reads both the same way: tasks, one entry a title with its key, and a skipped one marked skipped with the open task's key as sameAs (one title added alone also keeps created).
harbor add "Book the venue @Quinn by Friday !high #Website" reads the title in plain words, as the website's New task does: it adds "Book the venue" for Quinn, due Friday, high priority, in the Website project, and says what it read. A flag wins over the words (they stay in the title), --literal keeps the title exactly as typed, and --due takes the same words (--due "next friday", --due "in two weeks"). In the full-screen app, n reads a new task's title the same way.
harbor limit RR prints how many tasks each of a board's columns takes at once; harbor limit RR doing 8 changes one (1 to 20, or none for no limit), if you own the harbor. harbor projects --json carries each board's limits too.
harbor premortem runs a pre-mortem with your crew: --start asks everyone "it's after the end date and this project failed: what happened?", each person adds answers alone for five minutes, and then the answers show together on the project's Risks & issues tab, where each becomes a risk in one click. On its own it prints the question and the answers you can see. Once a project is Done, harbor voyage prints its voyage log (planned against actual dates, the biggest slips, the risks that came true, who closed the most, and the crew's lines) and adds yours. harbor messages PROJECT reads a project's Messages tab, one conversation for the whole project, and harbor messages PROJECT "TEXT" writes to it; @Name sends it to that person's Inbox. harbor chat is the same for any piece of work: harbor chat RR-42 reads a task's comments, harbor chat Footwear a program's messages, harbor chat Footwear "TEXT" --reply 2 replies under message [2], and --watch follows the conversation live, printing new lines as they come; in a terminal, type a line to post it. harbor chat @aya "TEXT" writes a direct message (the Chat page's), harbor chat @aya @ben "TEXT" writes to a group of just them, harbor chat @aya reads it (and --watch follows it), and harbor chats lists your direct messages; only the people in a chat can read it. harbor note leaves a note for later on a project: it stays sealed (the crew sees only that it's there and who left it) until its day, until one of the program's milestones is reached, or until the project turns Off track, and then it opens at the top of the project and in the brief. harbor sound TASK --ask crew takes a sounding: it asks you, the task's owner and whoever has open work on its project how many working days the task will take (--ask "Sam,Priya" picks who). Each person answers alone with harbor sound TASK --answer 4 --why "…", and nobody sees the others' numbers until everyone has; then harbor sound TASK shows the spread, an estimate when the guesses are close, or "talk about this first" when they're far apart, and --settle DAYS records what you agreed. harbor soundings lists them, the ones waiting on your answer first. harbor goals lists each portfolio's goals, off track first, with each key result's progress. harbor goal "TITLE" --new sets one, and harbor goal "GOAL" reads or changes one: --owner, --due, --why, --link "Ridge Runner" to count a program, project or task toward it, --kr "Stores signed" --target 40 to add a number key result and --kr "Stores signed" --at 12 to move it. harbor milestones lists a program's milestones soonest first, with how many of their tasks are done, who signs them off and what they wait on; harbor milestone "NAME" --new --program P --due DATE adds one, and harbor milestone "NAME" moves (--due), renames, ticks (--reached), sets who signs it off (--signs-off), or, if it's yours to sign, --approves it or asks for --changes. harbor reports prints the Reports page's dashboards, each chart as its numbers. harbor messages PROJECT --edit "TEXT" fixes your latest message there. harbor ashore lists the public holidays and time away in the next eight weeks; --country US,GB sets whose holidays the harbor takes and --person NAME --country DE one person's own, which the forecast and the weekly load then count as days off.
harbor brief --say turns the brief into the BBC's Shipping Forecast: each program an area, wind for late work, visibility for health, gale warnings for anything off track. It prints the forecast and speaks it with your computer's own voice (say on a Mac, Windows' speech, or espeak-ng on Linux, which you may need to install). With --json it prints the forecast and stays quiet.
Every command takes --json for the raw result (a refusal then comes out as {"error": "…"} on standard output, still with exit code 1), and harbor COMMAND --help shows just that command. Statuses are backlog, todo, doing, review and done. A DATE is YYYY-MM-DD, today, tomorrow, or +N for N days from today.
When you belong to more than one harbor, say which: --harbor NAME on the command, or harbor use NAME once (it's saved with your sign-in; harbor use none forgets it). With neither, the commands ask rather than guess, so nothing lands in the wrong harbor. The full-screen app shares the same choice: it opens the harbor harbor use set, asks which one the first time if none is set, and a harbor you switch to in the app becomes the one the commands use.
Harbor holds back what it would hold back in the app: finishing a task that still waits on another, or going past a column's limit. The CLI says so and names the flag that goes ahead (--confirm, --over-limit).
Every change shows in Harbor's History as yours, "via Harbor CLI". The commands never delete anything (harbor sync included: removing a task's file brings it back); the full-screen app can, as the website can, and asks first.
Another server
harbor login --server https://your-harbor.example (or HARBOR_SERVER). HARBOR_CONFIG_DIR moves the saved sign-in.
Developing
The commands are plain Node with no dependencies. The full-screen app is src/tui in the repository (React with Ink), bundled into dist/app.mjs by node cli/build.mjs; Ink and React are its only dependencies. npm test runs the CLI's tests against a stand-in Harbor; e2e/cli.test.mjs and e2e/terminal-app.test.mjs drive it against a real one.
License
MIT (see LICENSE). The rest of the Harbor repository is private.