Projects that hold a task or a note, newest activity first, with counts and paths. Empty ones are left out (empty_projects_omitted) but still resolve by slug or path.

Register a project by name. Usually unnecessary: get_context and create_task register one from cwd.

Set name, root_path, repo_url or summary. Right after a project is registered, a one-paragraph summary and repo_url are what make it legible from another machine.

Removes a project and everything under it. Not recoverable; confirm must be its slug. Ask the human first.

Fold a duplicate project into the real one, keeping both sides' tasks, entries, notes and paths -- for the same repository registered twice (todox and todox-2). from stops existing; confirm must be its slug. Not undoable: ask the human first, then set repo_url on the survivor.

The session-start briefing: standing rules, decisions, dead ends, open questions, open tasks with their linked files and the last handoff. Call it first, with cwd. Capped: fifty open tasks, three entries per kind per task (one handoff), and a byte budget on every body -- notes, task bodies and log entries -- smaller with a focus. Nothing is truncated: every record keeps its id and head (first line), and a body of null means the budget was already spent, never that the record is empty -- get_task and get_context_note read the rest. open_tasks_omitted/log_omitted count records NOT here; context_omitted/task_bodies_omitted/log_bodies_omitted count records here without a body. focus (one sentence on what this session is for) spends the budget on what is relevant instead of what is newest; context_ranked_by/log_ranked_by say which you got. Open tasks untouched for 14+ days come back head-only in idle_tasks -- title, status, days idle, last handoff head -- and cost no budget. summary_missing: true means nobody has said what this repository is: update_project with one or two sentences once you know.

Everything todox has recorded against a file: the tasks that touched it with their dead ends and decisions, and the context notes attached to it in full. Ask before editing a file you have not seen this session — a dead end costs nothing to read and an afternoon to rediscover. The path may be absolute or relative to the repository root; both fold to the same answer, so a note linked on one machine is found from another. Pass cwd or project to say which repository is being asked about.

Call before finishing. yours: the tasks you changed or wrote on in this project within hours (default 12), any status, each with whether a handoff was written since the last thing you did there. stale: tasks 'doing' for 7+ days with nothing logged, by anyone. Ids, titles, dates and one boolean -- small on purpose. Empty lists mean nothing is owed. hint says what to do about each list.

Tasks in a project, filtered by status.

One task, its whole log (newest 200; entries_omitted if more) and its linked files marked fresh/changed/missing.

Capture work that will not finish this session. Pass cwd and todox picks the project; registering a new one needs repo_root or repo_url too. Put the goal and the definition of done in body.

Change title, body, status or priority. 'doing' starts the clock, 'done' stops it; that is where report durations come from.

Append one entry: 'decision', 'dead_end', 'question', 'note' or 'handoff'. First line is the headline the briefing shows; keep the body to a screen. Settling an earlier question? Pass its id as answers_entry_id -- nothing else closes one.

For an entry that was wrong when written (wrong task, a decision never made). An entry overtaken by later work is history, not wrong: append instead. Not for tidying.

Attach file paths to a task (task_id) or a note (context_id), one or the other -- the files the work touches, and the plan it follows, wherever that lives: a path outside the repository is fine and a URL (a claude.ai artifact, say) is kept as written. todox can then warn when a linked file changes, and get_file_context can find the task or note from the path.

Remove a link whose file was deleted, renamed or attached by mistake. Nothing on disk is touched.

Clear the stale warning on a linked file once you have read the change and the note still holds (report its current hash first; hosted, via report_file_hashes). If the note no longer holds, fix the note instead.

The whole body of one context note -- for a note the briefing's budget did not reach (body null, never empty) or a search snippet you need the rest of. Entries are read with get_task.

Knowledge that outlives a task: decision, convention, gotcha, preference. Omit project and cwd to make it account-wide.

Rewrite a note that is wrong or out of date; body replaces the whole thing. Correct rather than add a second note that disagrees.

For a note that should never have been written (wrong project, or so superseded it misleads). Merely out of date: update_context.

Full-text search over tasks, log entries and notes across ALL your projects, ranked by relevance. Ask in words -- 'why did we choose scrypt over bcrypt' -- terms match independently and more matches rank higher; quote a phrase to require it. Stemmed in English and Turkish, with a substring match underneath so 'FileSync' finds readFileSync. Each hit carries a snippet from the matching part. Filters narrow, never search: kinds (['dead_end'] = has this been tried?, ['decision'] = why is it like this?; tasks have no kind), project (account-wide notes still come back). Leave both out unless the question has a shape. Not searched: file paths, project names. At most limit hits (default 30). Ask in the language the log is written in -- a Turkish note is found by a Turkish question -- and if a sentence finds nothing, retry with only the distinctive identifiers (3+ characters; shorter ones match as whole words only).

What got done in a window, from the log: tasks completed and opened, time in 'doing' and lead time, models, decisions, dead ends, open questions. format:'markdown' to hand on, 'json' to reason over. Prefer a named period to 'all'.