## Reference: every noun and its own words Every noun takes these words: all, attach, comment, comments, complete, create, delete, detach, files, find, folder, force_delete, index, link, linked_to, move, paths, react, read, read_all, reopen, restore, search, section, set, show, stamp, tag, unlink, unread, update. A noun that renames one says so below. journal --help prints every word with its arguments. ### message — What the user left for the agent, or the agent for the user A message is read once by the other side and processed part by part; what each part became is written on it. Scope: environment. Seen by: user, agent. Renamed: complete is processed. journal message archive journal message declare journal message edit journal message file [--into …] journal message process journal message recent journal message reply [--file …] journal message waiting ### todo — One thing to do later, with a brief that says why and where to start A to-do waits on the list until it is started as work and closed; auto mode works the list in order. Scope: environment. Seen by: user, agent. Renamed: complete is done. journal todo after [--off] journal todo answer journal todo ask [--set key=value…] journal todo assign journal todo block journal todo board [--plan …] [--agent …] [--lane …] [--after …] [--size …] [--query …] [--only …] journal todo delegate [--role …] [--given …] journal todo place journal todo priority journal todo prune [--days …] journal todo report journal todo shift [--why …] [--how …] journal todo start journal todo strike journal todo sweep journal todo task [--brief …] journal todo tasks <agent> journal todo touched <n> journal todo unassign <n> [--set key=value…] journal todo unblock <n> ### work — What the agent is doing right now, declared before its first write Work is opened by the agent, updated as it moves and ended when done; the agent that opened it has seen it. Scope: environment. Seen by: user. Renamed: complete is end, create is start. journal work active journal work await <words> [--n …] [--on …] journal work log <words> [--n …] journal work park <words> [--n …] journal work resume <n> ### doc — What stays true about the project, catalogued for every session A doc is written once, cited by facts and rules, and read before anything it settles is re-investigated. Scope: project. Seen by: user, agent. Renamed: complete is final. journal doc cut <n> <title> journal doc draft <n> journal doc file <title> <path> journal doc hide <n> journal doc keep <n> journal doc locate <words> journal doc revision <n> <number> journal doc revisions <n> journal doc supersede <n> <by> journal doc unhide <n> ### report — What was checked and what was found, written for the user, read once A report answers something the user asked to have checked; it ages out or becomes a doc. Scope: environment. Seen by: user, agent. Renamed: complete is archive. journal report changes journal report dismiss <n> journal report doc <n> journal report drop <n> <ref> journal report item <n> <section> <ref> <title> [--note …] journal report note <n> <ref> <text> journal report recap <summary> ### fact — Something true about this environment that a later session would get wrong without A fact is handed to every session on its environment; it is struck when it stops being true. Scope: environment. Seen by: user, agent. Renamed: complete is strike. journal fact promote <n> ### rule — A ruling that binds every environment of the project A rule is decided by the user, cited where it applies, and struck only by them. Scope: project. Seen by: user, agent. Renamed: complete is strike. journal rule inject <n> journal rule pin <n> journal rule reread journal rule uninject <n> ### reminder — An instruction said again until it is retired A reminder is repeated to the agent at each start and every so often while it works. Scope: environment. Seen by: user, agent. Renamed: complete is retire. ### question — Something the agent asks the user, with choices to pick A question waits for the user; its answer reaches the agent as an event. Scope: environment. Seen by: user, agent. Renamed: complete is answer, create is ask. journal question dismiss <n> [--why …] ### comment — What the user or the agent said about another resource A comment is a resource of its own, linked to what it is about. Scope: environment. Seen by: user, agent. Renamed: comment is reply, complete is done. ### agent — A session of Claude or Codex, and what it is doing right now The journal watches what the agent reports and tells whether it is idle, busy, working, or has compacted its conversation. Scope: environment. Seen by: nobody. journal agent appoint <session> journal agent bar journal agent by_session <session> journal agent changes journal agent control <session> <action> [--value …] journal agent edited_file <n> <id> [--side …] journal agent edited_image <n> <id> journal agent edits <n> [--since …] [--last …] journal agent family journal agent force <session> journal agent hooks <provider> journal agent keys <session> <text> journal agent keywords <skill> <keywords> journal agent links <n> [--subagent …] journal agent load_skill <skill> journal agent older_edits <n> <before> [--last …] journal agent online journal agent options <provider> [--model …] [--effort …] journal agent pause <session> journal agent permit <env> <decision> journal agent primary journal agent relaunch <session> [--skip] journal agent resume <session> journal agent retire <subagent> journal agent screen <session> [--since …] journal agent shell <session> <command> [--now] journal agent skill <skill> journal agent skills [--agent …] journal agent stop_task <n> <task> [--description …] journal agent transcript <n> [--subagent …] [--since …] [--before …] [--last …] [--entry …] journal agent wire <provider> <hooks> ### notification — Something the user should hear about, told to them once A notification is for the user: an update that landed, a plugin that installed, a setting the agent changed. The agent's own acts are not notifications; they are read in the activity. Scope: environment. Seen by: nobody. ### notice — One line pinned to the chat while it matters A notice stays until you close it or the agent closes it. It can have a colour and a link. Scope: environment. Seen by: user. Renamed: complete is close. ### reaction — A face on a message A reaction is one face by one actor on one message; the same face again takes it off. Scope: environment. Seen by: user, agent. ### tool — A script kept for a job that comes back, catalogued so the next agent runs it instead of writing it again A tool names its entry (how to run it), its usage and what it does; run executes it from the project root. Scope: project. Seen by: user, agent. journal tool run <n> <args> ### feature — A built-in part of the journal that can be switched on or off One row per feature the engine finds, carrying whether it is on. A row whose file is gone stays, switched off. Scope: environment. Seen by: nobody. journal feature cancel_update journal feature configure <name> <key> <value> journal feature new_features journal feature on <name> [--default] journal feature save <values> journal feature settings journal feature switch <name> [--on] journal feature sync_gmail journal feature sync_linear ### plugin — A repository installed into the journal: it hears the bus, answers, and may run services of its own Installed from a GitHub URL or a local path, fixed at one exact version; its manifest says what it listens to, what it runs and which pages it shows. Scope: project. Seen by: user, agent. Renamed: complete is remove. journal plugin clear_log <n> journal plugin configure <n> <key> [--value …] journal plugin disable <n> journal plugin enable <n> journal plugin install <source> [--ref …] [--yes] journal plugin preview <source> [--ref …] journal plugin purge <n> journal plugin raise <plugin> <event> <brief> [--open …] [--key …] journal plugin settle <plugin> <key> [--how …] journal plugin upgrade <n> [--ref …] [--yes] [--again] ### environment — One line of work with its own record: messages, to-dos, facts, plans, settings An agent works in one environment at a time. It can switch to a free one, or claim a taken one by giving a reason. Scope: project. Seen by: nobody. Renamed: complete is remove, create is prepare. journal environment attached [--kind …] [--shelf …] [--search …] [--last …] [--skip …] journal environment attachments journal environment claim <n> <why> journal environment code_pull <name> journal environment code_push journal environment connect [--address …] [--key …] journal environment connection journal environment disconnect journal environment events [--since …] [--last …] journal environment grant <n> [--off] journal environment hand <env> <to> journal environment launch <n> [--agent …] journal environment leave <n> journal environment manifest journal environment pickup <n> journal environment rename <n> <name> journal environment stop <n> journal environment summary journal environment sweep <n> [--yes] journal environment switch <n> [--project] [--move …] [--back] journal environment sync journal environment unarchive <name> journal environment unused <name> [--hint …] journal environment vacant <title> [--mine …] ### nudge — A short instruction the journal sends the agent by itself; you never see it in the chat. A nudge is written by a feature and spoken to the agent as it is; the user never hears it. Scope: environment. Seen by: agent. ### worktree — A git worktree handed to a helper, cut from the tip of the branch the project is working on The journal-todos skill says how it works. Scope: project. Seen by: user, agent. Renamed: complete is drop. journal worktree cut <name> [--helper …] [--packages] journal worktree drift <n> journal worktree renew <n> journal worktree take <n> [--reviewed] ### profile — How the agent talks to you: its voice, what it calls you and a sample line The journal-form-of-address skill says how it works. Scope: project. Seen by: user, agent. Renamed: complete is retire. journal profile anchor <n> <path> [--sits] [--seat …] [--line …] journal profile animations journal profile callings journal profile duplicate <n> journal profile namings journal profile samples journal profile schedule <n> [--plan …] journal profile schedules journal profile tune <n> <path> [--edit …] ### helper — An agent on any provider dispatched for one bounded job, in an environment of its own that stays out of the lists The journal-todos skill says how it works. Scope: environment. Seen by: user, agent. Renamed: complete is finish. journal helper allow_suite <n> journal helper dispatch <name> <job> [--provider …] [--model …] [--brief …] [--worktree] [--checkout …] [--todos …] [--packages] journal helper done <todo> <how> journal helper peers journal helper report <text> journal helper retire <n> [--why …] [--confirm] journal helper say <n> <text> [--todos …] journal helper stop <n> journal helper todo <n> journal helper transcript <n> [--since …] [--before …] [--last …] [--entry …] ### trigger — Words, or a fact in the journal, that the user watches for, and what the journal does when they come up The journal-triggers skill says how it works. Scope: project. Seen by: user. Renamed: complete is retire. ### sequence — Steps the agent follows in order, one at a time, started by hand or by a moment The journal-sequences skill says how it works. Scope: project. Seen by: user, agent. Renamed: complete is retire. journal sequence abandon <n> [--about …] [--why …] [--sure] journal sequence follow <n> [--about …] journal sequence include <n> <other> [--steps …] journal sequence next <n> [--about …] [--through …] journal sequence run <n> [--about …] journal sequence steps <n> <steps> ### board — A named board of tickets with stages of its own The journal-tickets skill says how it works. Scope: project. Seen by: user. journal board added <n> <tickets> journal board ask <n> <question> [--abstract …] [--set key=value…] journal board build <n> [--name …] [--steer …] journal board built <n> <summary> journal board cancel <n> journal board discard <n> [--why …] journal board expect <n> <count> [--fewer …] journal board follow_up <n> <text> [--idempotency …] journal board group <n> <name> <tickets> journal board hand <n> <document> [--text …] [--idempotency …] journal board ideas <n> <ideas> journal board keep <n> journal board log <n> <line> journal board meaning <n> <stage> [--meaning …] journal board orchestrate <mode> journal board outline <n> <sections> journal board pause <n> journal board pick <n> <tickets> journal board progress <n> <section> <state> [--drafts …] journal board request <n> <text> [--idempotency …] journal board resume <n> journal board retry <n> journal board revise <n> <text> [--idempotency …] journal board say <n> <line> journal board score <n> <score> [--reading …] [--goal …] [--done …] journal board stage <n> <name> [--meaning …] journal board stall <n> <why> journal board start <n> journal board wait <n> ### browser — What the agent asks of the tab the user is driving — a picture, its text, a click — answered by the extension The journal-browser-control skill says how it works. Scope: environment. Seen by: nobody. journal browser answer <n> <text> [--ok] [--files …] journal browser ask <op> <args> [--wait …] journal browser driving journal browser pending ### check — A script that says pass or fail about the project, run by hand, by its button, or every so many minutes The journal-checks skill says how it works. Scope: project. Seen by: user. Renamed: complete is retire. journal check fail <n> <why> journal check gate <n> <message> [--paths …] [--wait] journal check pass <n> [--note …] journal check run <n> [--wait] journal check sweep [--wait] journal check touched <n> ### collection — A named collection of any resources that belong together The journal-collections skill says how it works. Scope: environment. Seen by: user, agent. Renamed: complete is close. journal collection add <n> <refs> journal collection held_files <n> journal collection members <n> journal collection remove <n> <ref> ### critique — A design critique round: one read-only critic per lens looks at the app, and their findings gather into one report The journal-reports skill says how it works. Scope: environment. Seen by: user, agent. Renamed: complete is finish. journal critique recheck <n> <revised> journal critique round <what> [--critics …] [--lenses …] [--model …] ### dump — A pile the user drops in one place, which the agent sorts by subject and files straight into a collection The journal-dumps skill says how it works. Scope: environment. Seen by: user, agent. Renamed: complete is close. journal dump answer <n> <text> journal dump ask <n> <question> [--guesses …] journal dump choose <n> <pick> journal dump decline <n> <pick> journal dump direct <n> <how> journal dump dismiss <n> journal dump failed <n> <item> <why> journal dump filed <n> <item> <how> [--refs …] [--added …] journal dump items <n> journal dump log <n> <status> [--on …] [--making …] [--detail …] journal dump name <n> <title> journal dump note <n> <item> <insight> journal dump offer <n> <options> [--summary …] journal dump remove <n> journal dump say <n> <text> journal dump split <n> <parts> journal dump stop <n> ### plan — Ordered phases of to-dos with a goal, approved by the user before it runs The journal-plans skill says how it works. Scope: environment. Seen by: user, agent. Renamed: complete is finish. journal plan abandon <n> [--why …] journal plan approve <n> journal plan build <n> journal plan delegate <n> [--off] journal plan dismiss <n> journal plan from_doc <doc> journal plan park <n> journal plan phase <n> <title> [--when …] [--checkpoint] [--brief …] [--before …] journal plan phases <n> journal plan todos <n> <p> <todos> [--move] [--off] journal plan progress <n> journal plan ready <n> journal plan rephrase <n> <p> [--title …] [--when …] [--checkpoint …] [--brief …] journal plan continue <n> journal plan review <n> journal plan stage <n> <at> journal plan start <n> journal plan tickets <n> <p> <tickets> [--move] [--off] journal plan timeline <n> ### ticket — A piece of work on a board, from the user, an agent or an outside source, run in an environment of its own The journal-tickets skill says how it works. Scope: project. Seen by: user. journal ticket accept_dependencies <n> [--only …] [--why …] journal ticket agent_session <n> journal ticket app <n> journal ticket approve_plan <n> journal ticket bind <n> journal ticket board <n> [--lane …] [--after …] [--size …] [--query …] journal ticket clear_worktrees journal ticket confirm <n> [--why …] journal ticket continue_plan <n> journal ticket decline_dependencies <n> [--why …] journal ticket depend <n> <on> journal ticket gmail_reply <n> <text> journal ticket host <n> journal ticket keep_branches journal ticket linear_comment <n> <text> journal ticket merge <n> journal ticket organization journal ticket place <n> <before> journal ticket priority <n> <value> journal ticket queue_before <n> <other> journal ticket screen <n> [--lines …] journal ticket send_back <n> <note> journal ticket start <n> [--provider …] [--model …] journal ticket start_next <n> journal ticket status <n> journal ticket stop <n> journal ticket tell <n> <note> journal ticket todos journal ticket unhost <n> ### secret — A key or login the agent may use without ever seeing it The journal-secrets skill says how it works. Scope: project. Seen by: user, agent. journal secret allow_login <n> journal secret fill <n> <field> <value> journal secret login <n> journal secret propose_programs <n> <program> journal secret request <title> <why> [--kind …] [--url …] journal secret revoke_login <n> journal secret run <name> <command> [--stdin …] [--env] journal secret store <n> <field> <path> journal secret where ### suggestion — A change the agent proposes unasked; the user accepts, adjusts or declines it, and nothing waits The journal-suggestions skill says how it works. Scope: environment. Seen by: user, agent. Renamed: complete is decide, create is suggest, delete is withdraw. journal suggestion install <n> journal suggestion note_window <n> ### share — A link that lets someone outside the journal view one document, report, collection or plan, or the agents or chat view as they change, and nothing else The journal-sharing skill says how it works. Scope: project. Seen by: user, agent. Renamed: complete is stop. journal share agree <n> <words> journal share allow <n> journal share answering journal share approve <n> journal share ask <n> <question> <options> journal share check_tunnel journal share domains journal share install_tunler <host> journal share login <username> <password> [--endpoint …] [--master_password …] journal share logout journal share opens <ref> journal share reachable <n> journal share readdress journal share release <domain> journal share restart_tunnel journal share share_layout <name> <layout> [--expires …] [--once] journal share share_view <view> [--expires …] [--once] journal share tunnel journal share tunnel_cause journal share update_tunler journal share version ### phone — A phone the user connected by scanning a code, which reads the chat and acts as the user from anywhere The viewer's Connect your phone dialog shows the code; journal phone disconnect <n> cuts a phone off at once. Scope: project. Seen by: user, agent. Renamed: complete is disconnect. journal phone allow_passkey <n> journal phone connect [--days …] [--member …] journal phone refuse_passkey <n> ### output — The whole output of a command whose middle was cut from what the agent saw A shell command that prints more than twice output_lines is shown to the agent by its two ends; the whole output is kept here as a file, to grep or read by range. The last 50 are kept. Scope: environment. Seen by: nobody. journal output keep <path> [--command_line …] [--provider …] [--session_id …] [--shown …] ### record — A session recorded into a folder: every moment the journal's record or the project's files changed journal record start <folder> records alongside the session into that folder; journal record stop ends it and copies in the transcripts of the agents that ran. Scope: environment. Seen by: user, agent. journal record scrub <folder> journal record start <folder> journal record stop ### template — Instructions put in front of anything made from it, with the parts it starts with The journal-templates skill says how it works. Scope: project. Seen by: user, agent. Renamed: complete is retire. journal template field <n> <label> [--kind …] [--options …] [--default …]