Skip to content
KurrentDB

Session outcomes

A session’s Overview brings its outcome, tasks, artifacts, and context together. Open a session from Sessions or from a Dashboard outcome card.

The Outcome explains the work’s context, decisions, result, and unfinished work. It is a generated summary; use Transcript or Events to inspect the underlying evidence.

Outcomes are generated after a session ends, when a summary model is configured. They update in the page when available. If an ended session has no outcome, eligible owners and administrators can use Generate outcome.

Use the copy control to take the outcome into a review or handover.

Overview can show the task list and Artifacts such as plans, specs, and design documents. Open an artifact to read what the agent intended to do, then compare it with the outcome.

In v1.1.1, agents can explicitly record plans through the kcap-plans MCP server:

ToolPurpose
declare_plan_documentRecord a plan, spec, or design document.
set_plan_tasksRecord the ordered task list.
update_plan_taskUpdate a task as work starts, finishes, or is skipped.
get_planRead the plan and current task progress.

Ask the agent to keep the plan current as it works. A checked task is a recorded status; it is not independent proof that the work passed verification. Use Errors & plan validation to inspect completion.

Use the session’s work-item and PR links to follow the larger effort. A work item can bring together implementation, review, and follow-up sessions.

The Evaluation tab is the place to inspect scores and improvement suggestions. An outcome describes what happened; an evaluation assesses it.

Administrators configure the outcome model under Administration → AI & models → Summaries. A missing summary configuration does not stop session recording.

Ask your agent to recap a session or recall earlier work using its recorded summary and conversation.