Conversations, Traces, and Saved Queries

Longer agent sessions leave a trail you can resume and audit. The CLI stores conversations, execution traces, and optional named queries on disk under ~/.postsale/.

In this article, we will list and continue conversations, inspect and export traces, and save and re-run named intents.

Before We Begin

This article assumes that:

• You have run postsale run at least once if you want sample conversation or trace data

Conversations

Here's how:

postsale conversations
postsale conversations -n 20 --human
postsale run --continue "follow-up question"
postsale run --continue <id> "..."
postsale continue <id>

Default directory: ~/.postsale/conversations/ (POSTSALE_CONVERSATIONS_DIR to override).

For a longer back-and-forth in one sitting, postsale run --interactive keeps the session open: after each envelope, the CLI prompts on stdin for your next message until you exit. postsale continue <id> reopens a stored conversation the same way.

continue supports the same authorization and model flags as run. Check postsale continue --help.

When to continue vs start fresh

Traces

Here's how:

postsale traces list
postsale traces show <id-or-prefix>
postsale traces export <id>
postsale traces purge --yes

Agent tool: query_trace.

Every trace records which credential ran it as identity: { kind, id }: kind is session or api_key, and id is the session's subject or the key's 8-character display id. postsale traces export <id> --format markdown renders it as a Credential line.

Saved queries, stored on this machine

These are local named intents, not server-side Postsale filters (postsale filters).

Here's how:

postsale saved-queries save weekly "how many orders last week"
postsale saved-queries list
postsale saved-queries run weekly
postsale saved-queries delete weekly --yes

Alias: postsale sq. Money-moving still requires --yes or --authorize on run.

Good to Know

Additional Reading

• Use natural language with postsale run
• Batches and Unattended Runs