Sessions & Conversations

A session is the container that keeps your current work coherent. It holds the conversation history, the active task context, approval state, and the tools available for that piece of work.

Why sessions matter

• They stop unrelated work from blending together.
• They preserve context between turns so you do not have to repeat yourself.
• They let Gestura keep track of approvals and tool use.
• They make troubleshooting easier because you can reason about one workflow at a time.

What a session typically contains

• Conversation history: your prompts, Gestura's replies, and any clarifying turns.
• Task state: work that has started, finished, or needs your approval.
• Tool context: built-in tools and MCP servers that are available to the session.
• Permission overrides: temporary trust changes for that specific workflow.

When to start a new session

• When you switch from one project or topic to another.
• When you want a cleaner context window and fewer assumptions from prior work.
• When you need different permissions or a different toolset.
• When a previous workflow became noisy or unfocused.

How sessions stay manageable

Gestura includes context-management settings such as auto-compaction and compaction strategies. That means longer conversations can be summarized, truncated, or otherwise reduced before they become too large for the model you selected.

Practical advice

• Use one session per meaningful task stream.
• Keep approval-sensitive work separate from brainstorming.
• When results start drifting, either restate the goal clearly or start a fresh session.