Session

Many teams treat Session as a chat tab, then hit the same problems:

• goals drift and output quality drops
• parallel threads fight each other’s state
• coming back later feels like starting from zero

In Tentarc, a Session is a continuous execution lane for one objective.

What you feel immediately

• continuity: one objective keeps progressing in one thread
• recoverability: restart/crash/window switches don’t break the lane
• traceability: decisions and actions stay reviewable in one place

When to open a new Session

• the objective changes
• the risk boundary changes
• the collaboration boundary changes

Rule of thumb: same objective, same Session; new objective, new Session.

Three practical rules

• one objective per Session
• use follow-up turns instead of parallel competing threads
• for stable replay, keep workingDirectory, sources, and model fixed

Under the hood

If you need implementation details, Session persists under workspace with:

• session.jsonl for transcript
• attachments/ for files
• plans/ for planning artifacts
• execution-state.json for recovery state

You don’t need these files daily, but they are why Session is recoverable and auditable.