Sessions

A Session is one conversation with RunWield. Sessions are saved automatically, so you can resume them later in the terminal or in Workspace.

For the Session tree, forking, cloning, and compaction, see Pi Sessions and Pi Compaction.

Starting and resuming

Run wld to start a Session. Inside it:

/resume          # browse and resume recent Sessions
/new             # start a fresh Session
/name <name>     # name the current Session
/name            # show the current name
/session         # show Session information and token totals
/context         # show how much of the model's context window is in use
/compact         # compact the conversation to free context
/export          # export the complete Session to HTML
/export out.json # export raw entries from every segment to JSON
/share           # share HTML and JSON in one secret Gist with a preview link

RunWield saves Sessions under ~/.wld/sessions/.

When you resume a large Session, RunWield can offer to compact it first. Set the threshold with compactOnResumeThresholdPercent.

Exporting and sharing

/export includes all committed planning, execution, and repair segments, plus Session details, artifacts, and Plan Associations. With no path it writes a timestamped HTML file in the Session’s project directory. Use /export out.json for a versioned JSON document with each segment’s raw entries. .jsonl export is retired; use .json instead.

HTML works offline and shows segment headings, Markdown messages, expandable tool calls, and collapsed thinking. Image attachments appear as [image]; JSON keeps their raw data. Export does not change the Session. During a turn it includes only the last committed history. In-memory helper Agent transcripts and Background Task logs are not included; their results are included when recorded in the parent Session.

/share requires the authenticated GitHub CLI. It uploads runwield-session.html and runwield-session.json to one secret Gist and prints the Gist URL and a gistpreview.github.io HTML preview link. Anyone with the secret Gist link can read both files, including thinking and full tool output. Check the content before sharing. The preview uses an external service; the Gist link remains available if that service is down.

Session names

A new Session’s terminal title is wld - <folder>. Once the Router has sorted your first request, it names the Session, and the title becomes wld - <name>. A name you set with /name always wins; the Router never replaces it.

Which Agent answers

Every new Session starts with the Router. After it hands your request to an Agent, that Agent keeps answering your follow-up messages. Use /agent <name> to switch Agents, /agent router to route your next message again, or /new to start over. See How requests are routed.

Continuing in Workspace

The same Session can continue in Workspace on another screen, including your phone. See Workspace.

Background tasks

Agents can run long commands, such as a test suite, in the background and keep working while they run. They can also ask a read-only helper Agent to investigate something in the background.

• Up to five background tasks can run at once in a Session.
• The Agent gets each result when it finishes, during its current turn or a later one. Long output is saved to a log file that the result points to.
• Closing a browser tab or finishing a turn doesn’t stop background tasks. Pressing Stop, or quitting RunWield, cancels them.
• Background tasks belong to the RunWield process that started them. If that process exits, they can’t be resumed.
• When an Agent tries to finish while tasks are still running, RunWield warns it first. If it finishes anyway, the remaining tasks are cancelled. A cancelled test run is not a passing test run.