Filter by project or energy when narrowing existing work. Use
    session_digest when you want a session-start summary with reminders and
    resume context instead of the raw thread list.
    

    Use for project discovery or navigation. This is read-only; use
    resolve_project or upsert_project when a project needs to be resolved or
    changed.
    

    Use at session start before session_digest. With create_if_missing=true,
    this may create a local project registry entry; set it false when lookup
    must be read-only. Use upsert_project for explicit metadata or forge
    configuration changes.
    

    Use when the project identity should change. This request does not apply
    the rename immediately; list_pending_actions shows queued confirmations.
    

    Nothing is deleted immediately. The flags describe what the confirmed
    action should remove; use list_pending_actions to inspect the queued
    request before confirmation.
    

    This is read-only and is useful after rename_project or delete_project to
    show the operator exactly what remains pending.
    

    One thread should represent one independently finishable outcome, not a
    whole project. Pass thread_id when updating a known thread. For routine
    checkpoints on active work, prefer upsert_progress so progress notes and
    PROGRESS.md stay in sync.
    

    Prefer a known thread_id so the checkpoint cannot land on the wrong
    thread. If selection is ambiguous the tool can request a thread_id;
    force_new_thread explicitly starts another outcome. Depending on
    create_thread_if_missing, a missing thread may be created as a side effect.
    

    Use only with a known thread_id after the work is actually finished.
    Use pause_thread for unfinished work that will resume later, or
    dismiss_thread when intentionally abandoning it. note is an optional
    completion note.
    

    Use when the thread will continue later. This updates its pause/resume
    state; use mark_done for completed work or dismiss_thread for work being
    intentionally abandoned. Requires the exact thread_id and next_step.
    

    Use for abandoned, superseded, or no-longer-relevant work. Use mark_done
    when the intended outcome was completed, or pause_thread when it will be
    resumed later.
    

    Prefer due_only=true at session start to surface only reminders that need
    attention now. Set include_handled=true only when historical handled
    reminders are relevant.
    

    Includes counts, next-up work, and due reminders. Use session_digest when
    you also need project-specific resume context or the progress wiki snippet.
    

    Side effect: this persists the workspace/project mapping and, when
    create_open_thread=true, also creates a default open thread. Use
    resolve_project when you only need to resolve an already-known workspace
    or want optional lookup-with-create behavior.
    

    kind selects once, session, daily, or random scheduling. due_at_iso is an
    ISO datetime used for a once reminder when a specific due time is known.
    Use list_reminders to read existing reminders without creating one.
    

    Use after resolve_project. It combines relevant stale/open threads, due
    reminders, and the progress wiki snippet; query narrows overlap relevance
    and energy can filter work to the operator's current capacity.
    

    This has an external side effect and depends on the operator's OpenClaw
    integration being configured. It sends a compact Hub-generated digest,
    not raw chats; project_slug narrows it and note adds short context.