Imported from jessegall/agent-journal (.codex/skills/journal/SKILL.md). Install upstream with npx skills add jessegall/agent-journal --skill journal. Copyright stays with the author.

The journal

If you are a subagent, stop here. The journal is the main conversation's; report what you found and it files what matters. Reads are fine.

A compaction keeps what was done and drops what was decided. The journal is the record of what was decided, handed back to you at every start, and the engine beside your terminal is what tells you what to read next. You never poll it: when something is owed — a message the user left, a question answered, a reminder, the next row under auto — the engine types one line into your terminal while you are idle, in a tiny vocabulary: message 3 created, 2 unseen question, work 1 open, todo 5 next, or a nudge in plain words. Read it as a line from the user's side and act on it.

Everything runs through one command, journal, and every command is a noun and a word: journal <type> <word> …. The nouns are the resource types; the words are the one controller's methods, renamed by the type where the type has its own word (a to-do is added and done, work started and ended, a question asked and answered, a pin struck, a report archived, a plan acknowledged, a message processed). Every resource has a title (at most 80 characters, never a colon), an abstract, a brief, sections, links, comments, who has seen it, and an outcome written when it completes. journal <type> --help lists the words; the reference at the end lists every noun.

When the user asks for work

1. It is the current work, a step of it, or a correction: carry on; journal work section <n> "<what moved>" "<how far>" when the direction changes.
2. It is different. A to-do — the default: journal todo add "<title>" --brief "<why, where to start>", say "parked as to-do n", and carry on. Its words: journal todo ask <n> "<question>" files a question on the row and the row waits; todo answer <n> "<text>" answers it; todo block <n> "<why>" / todo unblock <n>; todo after <n> <m> says it waits on row m (--off undoes); todo strike <n> "<why>" abandons it on the record; todo start <n> opens work for it; todo prune --days 30 drops long-closed rows. The list is ordered by priority, then number: journal todo priority <n> low|default|high|critical (or a number; 100 is default) when the user says something comes first.
3. It is different and the user said NOW — their word, not your judgement: update the open work with where it got to, then start the new one.

With nothing open, the request is the work: read until you can name it, journal work start "<the work>", go. Declare before the first write: a write with no work open is refused by the gate. journal todo start <n> opens work for a row; journal work end <n> --how "<what landed>" ends it, and the row is closed only by journal todo done <n> --how "<how>" — ending work is not finishing a row. journal work update <n> --brief "<where it got to>" records a turn in the work; work section a longer part. A commit closes a row when its message carries Journal: todos done <n> at column 0.

"I'll do it after this" is a to-do, every time. The deferral feature names the sentence back to you if nothing was parked.

Tag every message

Open every message with exactly one tag: [!discovery] [!correction] [!blocked] [!info] [!reply]. When in doubt, [!reply]. The tags feature tells you once if the last message had none.

Pin, rule, reminder, or nothing

Would a later reader be WRONG without it? a pin. Will you stop DOING it though you know? a reminder. One thing to do later? a to-do. Binds every environment? a rule. Pins and rules carry their reasoning in the brief. At each mark of the context window (the context feature's marks) writes are held until you decide: journal pin create "<claim>", journal rule create "<ruling>", or journal nothing "<why>".

Messages, questions, comments

The user writes to you from the viewer. journal message unread lists what waits, journal message read <n> marks one seen. Use journal message process <n> "<their exact words>" "<resource ref>" only when that part became a record resource such as a to-do, pin, rule, reminder, question, doc, report, plan or work. The pills above a message are links, never status prose, acknowledgements or descriptions of what you did. Reply with journal message reply <n> "<text>" [--file <path>] when the message needs an answer; react when it only needs acknowledgement; then close it with journal message processed <n> --how "<what was done>". message waiting lists the ones not yet processed; message file <n> <name> --into "doc <d>" files an attached file into a doc (keep keeps it); message archive <n> "<why>" puts one away; message edit <n> "<text>" rewords one that still waits. Ask through the journal, never by halting: journal question ask "<one line>" --abstract "<context>" --set about=todo:<n> with options as --set options=… JSON; the answer reaches you as an event. A comment the user left is handled and journal comment done <n> --how "<what was done>".

Plans, reports, docs

The tab the user is driving is yours to look at, once they press the wheel in the chat window's bar: journal browser ask shot (a picture, attached to the ask), ask text, ask url, ask dom, ask console, ask click "<selector>", ask type "<selector>" "<words>", ask goto <url>, ask eval "<js>", ask scroll top|bottom|<selector>. Each waits up to 30 seconds for the extension's answer and prints it; with no tab being driven it is refused and says so.

An acknowledgement is a reaction. A message that needs no answer — "noted", "carry on", a nod — gets journal message react <n> "👍" (one of 👍 ❤️ 🎉 😄 👀 🙏 👎 💔 😠) instead of words; a reaction also sits fine beside a pill, on a message you filed a to-do from, and beside a reply. Reply when there is something to say.

A subagent that must write is lent an environment, never detected. journal environment <n> grant lends this environment to this session's subagents; paste into the dispatch prompt that every journal command runs as journal --env="<name>" --agent="<its-id>" …. Its rows land in the same record marked with that id; it may write messages, to-dos, work, questions, comments, reports, plans — never a pin, rule, reminder, suggestion, doc, tool or style, and it never switches, claims or grants. journal todo assign <n> --to="<id>" hands it one row nobody else may take; it reports with journal todo report <n> "<how>" and you close the row with todo done. Twenty silent minutes clear an assignment and tell you (agents.lapse). Most subagents need none of this: they report, and you file.

A change nobody asked for is a suggestion, not a sentence in your reply: journal suggestion suggest "<the change>" --brief "<what you saw, what it costs now and later>". Nothing waits on it; the user accepts, adjusts or declines it in the viewer, an accept or adjust files a to-do that cites it, and a decline is a ruling — you do not propose it again in other words (--set despite=true --set because="<what changed>" if something did). At most five wait at a time. Withdraw one that stopped being true: journal suggestion withdraw <n> --why "<why>".

Phases, a roadmap, "first … then …" is a plan: journal plan create "<name>" --set goal="<what is true when done>", journal plan phase <n> "<title>" --when "<complete when>" [--checkpoint], journal plan todos <n> <p> <rows…>, journal plan ready <n>. Only the user activates it and continues it past a checkpoint, in the viewer; the plan advances by itself as rows close. Research ends in a report you write: journal report create "<what was asked>" --brief "<answer, evidence, what was fine, where it stands>". What stays true is a doc: journal doc create, journal doc section <n> "<part>" "<body>", journal doc attach <n> <path> "<what it is>"; cite it with a link. doc draft <n> marks it unfinished, doc final <n> settled, doc supersede <n> --by <m> points readers of an old one at the new, doc detach <n> <name> drops a file (kept under struck/), doc index <n> catalogues files already in its folder, doc paths <n> prints their absolute paths; doc delete <n> "<why>" archives it.

Environments and sessions

A session works one environment; journal environment switch <n> takes a free one (--project also makes it the project's start environment, --move <session> moves another session, --back returns), journal environment claim <n> "<why>" a held one (the holder is told), journal environment prepare "<name>" makes one, journal environment rename <n> "<name>" renames it (the folder moves and every session on it follows), journal environment remove <n> [--yes] takes it away — its record goes to .journal/attic/ and the name is free again; --yes when rows are still open. journal environment pickup <n> shows what waits on one before you take it. Never switch on your own initiative. A subagent that must write is lent one: journal environment grant <n>, and it runs every command with --env <name> --agent <its-id>.

Look before you answer

journal search <term>, journal conversation --back 1 (the stretch the last summary replaced), journal user (the user's own words), journal carry (everything standing, in full), journal status.

Skills

The start block names the skills to load before the first write — every journal-* skill until the user chooses otherwise on the viewer's Skills page, where each skill has a Load button (a message asking you to load it now) and an every-start switch. Load what the block names with the Skill tool, then work; the skills feature reminds you every 25 tool uses if no journal skill is in the window, because a compaction empties it.

Features

Every capability is a feature the engine loads, switchable per environment in the viewer's Settings and tuned by its trigger. Each has its own skill, journal-<feature>, generated from the feature itself.

Reference: every noun and its words

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. journal message all [--deleted] journal message archive journal message attach [--what …] journal message comment journal message comments journal message processed [--how …] [--set key=value…] journal message create [--abstract …] [--brief …] [--set key=value…] journal message declare journal message delete [--why …] journal message detach [--why …] journal message edit journal message file [--into …] journal message files journal message find journal message folder journal message force_delete journal message index journal message link journal message linked_to journal message move journal message paths journal message process journal message react journal message read journal message reply [--file …] journal message restore journal message search journal message section journal message set journal message show journal message tag journal message unlink journal message unread [--actor …] journal message update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…] 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. journal todo after [--off] journal todo all [--deleted] journal todo answer journal todo ask [--set key=value…] journal todo assign [--to …] [--off] journal todo attach [--what …] journal todo block journal todo comment journal todo comments journal todo done [--how …] [--set key=value…] journal todo add [--abstract …] [--brief …] [--set key=value…] journal todo delete [--why …] journal todo detach [--why …] journal todo files journal todo find journal todo folder journal todo force_delete journal todo index journal todo link journal todo linked_to journal todo move journal todo paths journal todo priority journal todo prune [--days …] journal todo react journal todo read journal todo report journal todo restore journal todo search journal todo section journal todo set journal todo show journal todo start journal todo strike journal todo tag journal todo unblock journal todo unlink journal todo unread [--actor …] journal todo update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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. journal work all [--deleted] journal work attach [--what …] journal work comment journal work comments journal work end [--how …] [--set key=value…] journal work start [--abstract …] [--brief …] [--set key=value…] journal work delete [--why …] journal work detach [--why …] journal work files journal work find journal work folder journal work force_delete journal work index journal work link journal work linked_to journal work move journal work paths journal work react journal work read journal work restore journal work search journal work section journal work set journal work show journal work tag journal work unlink journal work unread [--actor …] journal work update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

plan — Ordered phases of to-dos with a goal, approved by the user before it runs

A plan is drafted by the agent, approved and continued by the user, and worked phase by phase. Scope: environment. Seen by: user, agent. journal plan abandon [--why …] journal plan activate journal plan all [--deleted] journal plan attach [--what …] journal plan comment journal plan comments journal plan acknowledge [--how …] [--set key=value…] journal plan create [--abstract …] [--brief …] [--set key=value…] journal plan delete [--why …] journal plan detach [--why …] journal plan files journal plan find journal plan folder journal plan force_delete journal plan from_doc journal plan index journal plan link journal plan linked_to journal plan move journal plan paths journal plan phase [--when …] [--checkpoint] [--brief …] [--before …] journal plan phases journal plan todos [--move] [--off] journal plan react journal plan read journal plan ready journal plan rephrase [--title …] [--when …] [--checkpoint …] [--brief …] journal plan restore journal plan continue journal plan search journal plan section journal plan set journal plan show journal plan tag journal plan unlink journal plan unread [--actor …] journal plan update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

doc — What stays true about the project, catalogued for every session

A doc is written once, cited by pins and rules, and read before anything it settles is re-investigated. Scope: project. Seen by: user, agent. journal doc all [--deleted] journal doc attach [--what …] journal doc comment journal doc comments journal doc final [--how …] [--set key=value…] journal doc create [--abstract …] [--brief …] [--set key=value…] journal doc delete [--why …] journal doc detach [--why …] journal doc draft journal doc files journal doc find journal doc folder journal doc force_delete journal doc index journal doc link journal doc linked_to journal doc move journal doc paths journal doc react journal doc read journal doc restore journal doc search journal doc section journal doc set journal doc show journal doc supersede journal doc tag journal doc unlink journal doc unread [--actor …] journal doc update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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. journal report all [--deleted] journal report attach [--what …] journal report comment journal report comments journal report archive [--how …] [--set key=value…] journal report create [--abstract …] [--brief …] [--set key=value…] journal report delete [--why …] journal report detach [--why …] journal report doc journal report files journal report find journal report folder journal report force_delete journal report index journal report link journal report linked_to journal report move journal report paths journal report react journal report read journal report restore journal report search journal report section journal report set journal report show journal report tag journal report unlink journal report unread [--actor …] journal report update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

pin — A fact a later session would get wrong without

A pin is handed to every session on its environment; it is struck when it stops being true. Scope: environment. Seen by: user, agent. journal pin all [--deleted] journal pin attach [--what …] journal pin comment journal pin comments journal pin strike [--how …] [--set key=value…] journal pin create [--abstract …] [--brief …] [--set key=value…] journal pin delete [--why …] journal pin detach [--why …] journal pin files journal pin find journal pin folder journal pin force_delete journal pin index journal pin link journal pin linked_to journal pin move journal pin paths journal pin promote journal pin react journal pin read journal pin restore journal pin search journal pin section journal pin set journal pin show journal pin tag journal pin unlink journal pin unread [--actor …] journal pin update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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. journal rule all [--deleted] journal rule attach [--what …] journal rule comment journal rule comments journal rule strike [--how …] [--set key=value…] journal rule create [--abstract …] [--brief …] [--set key=value…] journal rule delete [--why …] journal rule detach [--why …] journal rule files journal rule find journal rule folder journal rule force_delete journal rule index journal rule inject [--into …] journal rule link journal rule linked_to journal rule move journal rule paths journal rule pin journal rule react journal rule read journal rule restore journal rule search journal rule section journal rule set journal rule show journal rule tag journal rule uninject [--into …] journal rule unlink journal rule unread [--actor …] journal rule update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

reminder — An instruction said again until it is retired

A reminder repeats at every start and every so often mid-work, because knowing is not doing. Scope: environment. Seen by: user, agent. journal reminder all [--deleted] journal reminder attach [--what …] journal reminder comment journal reminder comments journal reminder retire [--how …] [--set key=value…] journal reminder create [--abstract …] [--brief …] [--until …] [--set key=value…] journal reminder delete [--why …] journal reminder detach [--why …] journal reminder files journal reminder find journal reminder folder journal reminder force_delete journal reminder index journal reminder link journal reminder linked_to journal reminder move journal reminder paths journal reminder react journal reminder read journal reminder restore journal reminder search journal reminder section journal reminder set journal reminder show journal reminder tag journal reminder unlink journal reminder unread [--actor …] journal reminder update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

suggestion — A change the agent proposes unasked; the user accepts, adjusts or declines it, and nothing waits

Accepting or adjusting files a to-do from it; a decline is a ruling the agent does not propose again. Scope: environment. Seen by: user, agent. journal suggestion all [--deleted] journal suggestion attach [--what …] journal suggestion comment journal suggestion comments journal suggestion decide [--how …] [--set key=value…] journal suggestion suggest [--abstract …] [--brief …] [--set key=value…] journal suggestion withdraw [--why …] journal suggestion detach [--why …] journal suggestion files journal suggestion find journal suggestion folder journal suggestion force_delete journal suggestion index journal suggestion link journal suggestion linked_to journal suggestion move journal suggestion paths journal suggestion react journal suggestion read journal suggestion restore journal suggestion search journal suggestion section journal suggestion set journal suggestion show journal suggestion tag journal suggestion unlink journal suggestion unread [--actor …] journal suggestion update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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. journal question all [--deleted] journal question attach [--what …] journal question comment journal question comments journal question answer [--how …] [--set key=value…] journal question ask [--abstract …] [--brief …] [--set key=value…] journal question delete [--why …] journal question detach [--why …] journal question files journal question find journal question folder journal question force_delete journal question index journal question link journal question linked_to journal question move journal question paths journal question react journal question read journal question restore journal question search journal question section journal question set journal question show journal question tag journal question unlink journal question unread [--actor …] journal question update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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. journal comment all [--deleted] journal comment attach [--what …] journal comment comment journal comment comments journal comment done [--how …] [--set key=value…] journal comment create [--abstract …] [--brief …] [--set key=value…] journal comment delete [--why …] journal comment detach [--why …] journal comment files journal comment find journal comment folder journal comment force_delete journal comment index journal comment link journal comment linked_to journal comment move journal comment paths journal comment react journal comment read journal comment restore journal comment search journal comment section journal comment set journal comment show journal comment tag journal comment unlink journal comment unread [--actor …] journal comment update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

agent — A session of Claude or Codex, and what it is doing right now

The hooks report activity; the engine distinguishes idle, busy, declared work and compaction. Scope: environment. Seen by: nobody. journal agent all [--deleted] journal agent attach [--what …] journal agent by_session journal agent comment journal agent comments journal agent complete [--how …] [--set key=value…] journal agent create [--abstract …] [--brief …] [--set key=value…] journal agent delete [--why …] journal agent detach [--why …] journal agent files journal agent find journal agent folder journal agent force_delete journal agent index journal agent link journal agent linked_to journal agent move journal agent paths journal agent react journal agent read journal agent restore journal agent search journal agent section journal agent set journal agent show journal agent tag journal agent unlink journal agent unread [--actor …] journal agent update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

notification — What the agent did, told to the user once

A notification is written for the user by a feature for every act of the agent, or by the agent to say a long piece of work landed. Scope: environment. Seen by: nobody. journal notification all [--deleted] journal notification attach [--what …] journal notification comment journal notification comments journal notification complete [--how …] [--set key=value…] journal notification create [--abstract …] [--brief …] [--set key=value…] journal notification delete [--why …] journal notification detach [--why …] journal notification files journal notification find journal notification folder journal notification force_delete journal notification index journal notification link journal notification linked_to journal notification move journal notification paths journal notification react journal notification read journal notification restore journal notification search journal notification section journal notification set journal notification show journal notification tag journal notification unlink journal notification unread [--actor …] journal notification update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

notice — One line kept over the chat while it matters

A notice stays until the user's X or the agent's close; a tone and a link may ride on it. Scope: environment. Seen by: user. journal notice all [--deleted] journal notice attach [--what …] journal notice comment journal notice comments journal notice close [--how …] [--set key=value…] journal notice create [--abstract …] [--brief …] [--set key=value…] journal notice delete [--why …] journal notice detach [--why …] journal notice files journal notice find journal notice folder journal notice force_delete journal notice index journal notice link journal notice linked_to journal notice move journal notice paths journal notice react journal notice read journal notice restore journal notice search journal notice section journal notice set journal notice show journal notice tag journal notice unlink journal notice unread [--actor …] journal notice update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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. journal reaction all [--deleted] journal reaction attach [--what …] journal reaction comment journal reaction comments journal reaction complete [--how …] [--set key=value…] journal reaction create [--abstract …] [--brief …] [--set key=value…] journal reaction delete [--why …] journal reaction detach [--why …] journal reaction files journal reaction find journal reaction folder journal reaction force_delete journal reaction index journal reaction link journal reaction linked_to journal reaction move journal reaction paths journal reaction react journal reaction read journal reaction restore journal reaction search journal reaction section journal reaction set journal reaction show journal reaction tag journal reaction unlink journal reaction unread [--actor …] journal reaction update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

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 all [--deleted] journal tool attach [--what …] journal tool comment journal tool comments journal tool complete [--how …] [--set key=value…] journal tool create [--abstract …] [--brief …] [--set key=value…] journal tool delete [--why …] journal tool detach [--why …] journal tool files journal tool find journal tool folder journal tool force_delete journal tool index journal tool link journal tool linked_to journal tool move journal tool paths journal tool react journal tool read journal tool restore journal tool run journal tool search journal tool section journal tool set journal tool show journal tool tag journal tool unlink journal tool unread [--actor …] journal tool update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

style — One rule of the project's coding style, on one subject, written as a skill

A style rule names its subject and its decision; the style feature writes the skill for it. Scope: project. Seen by: user, agent. journal style all [--deleted] journal style attach [--what …] journal style comment journal style comments journal style strike [--how …] [--set key=value…] journal style create [--abstract …] [--brief …] [--set key=value…] journal style delete [--why …] journal style detach [--why …] journal style files journal style find journal style folder journal style force_delete journal style index journal style link journal style linked_to journal style move journal style paths journal style react journal style read journal style restore journal style search journal style section journal style set journal style show journal style tag journal style unlink journal style unread [--actor …] journal style update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

connection — A service the project can reach, and which variable holds its token

Never the token itself: the name of the variable that holds it. Scope: project. Seen by: user, agent. journal connection all [--deleted] journal connection attach [--what …] journal connection comment journal connection comments journal connection complete [--how …] [--set key=value…] journal connection create [--abstract …] [--brief …] [--set key=value…] journal connection delete [--why …] journal connection detach [--why …] journal connection files journal connection find journal connection folder journal connection force_delete journal connection index journal connection link journal connection linked_to journal connection move journal connection paths journal connection react journal connection read journal connection restore journal connection search journal connection section journal connection set journal connection show journal connection tag journal connection unlink journal connection unread [--actor …] journal connection update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

environment — One line of work with its own record: messages, to-dos, pins, plans, settings

A session works one environment at a time; switch takes one that is free, claim takes a held one with a reason. Scope: project. Seen by: nobody. journal environment all [--deleted] journal environment attach [--what …] journal environment claim journal environment comment journal environment comments journal environment remove [--how …] [--yes] [--set key=value…] journal environment prepare [--abstract …] [--brief …] [--set key=value…] journal environment delete [--why …] journal environment detach [--why …] journal environment files journal environment find journal environment folder journal environment force_delete journal environment grant [--off] journal environment index journal environment leave journal environment link journal environment linked_to journal environment move journal environment paths journal environment pickup journal environment react journal environment read journal environment rename journal environment restore journal environment search journal environment section journal environment set journal environment show journal environment switch [--project] [--move …] [--back] journal environment tag journal environment unlink journal environment unread [--actor …] journal environment update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

browser — What the agent asks of the tab the user is driving — a picture, its text, a click — answered by the extension

journal browser shot|url|text|dom|console|click |type |goto |eval |scroll top|bottom|; the user turns driving on in the chat window's bar. Scope: environment. Seen by: nobody. journal browser all [--deleted] journal browser answer [--ok] [--files …] journal browser ask [--wait …] journal browser attach [--what …] journal browser comment journal browser comments journal browser complete [--how …] [--set key=value…] journal browser create [--abstract …] [--brief …] [--set key=value…] journal browser delete [--why …] journal browser detach [--why …] journal browser driving journal browser files journal browser find journal browser folder journal browser force_delete journal browser index journal browser link journal browser linked_to journal browser move journal browser paths journal browser pending journal browser react journal browser read journal browser restore journal browser search journal browser section journal browser set journal browser show journal browser tag journal browser unlink journal browser unread [--actor …] journal browser update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]

nudge — A line a feature has the engine type to the agent

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. journal nudge all [--deleted] journal nudge attach [--what …] journal nudge comment journal nudge comments journal nudge complete [--how …] [--set key=value…] journal nudge create [--abstract …] [--brief …] [--set key=value…] journal nudge delete [--why …] journal nudge detach [--why …] journal nudge files journal nudge find journal nudge folder journal nudge force_delete journal nudge index journal nudge link journal nudge linked_to journal nudge move journal nudge paths journal nudge react journal nudge read journal nudge restore journal nudge search journal nudge section journal nudge set journal nudge show journal nudge tag journal nudge unlink journal nudge unread [--actor …] journal nudge update [--title …] [--abstract …] [--brief …] [--outcome …] [--set key=value…]