Persistent Task Sessions

A Sypha Session represents the technical lifecycle of your interaction. It persistently retains your repository anchoring, active task objectives, and conversational history, enabling you to suspend and resume development without context degradation.

Data Persistence Registry

A session encapsulates:

• The specific Repository Anchor for the task.
• The complete Interaction Ledger (prompts, replies, and logic chains).
• Task-specific metadata and Git context (snapshots of the technical state).

Resuming Workflows

1. Access the Session History via the dashboard or integrated extension menu.
2. Select the target session to re-initialize; the dashboard will automatically restore all historical reasoning and context.

Shared & Detached Sessions (Forking)

• Shared Access: Generate a read-only, public URI for your session by executing /session share.
• Logic Forking: Team members can "fork" a shared session to create an independent copy, allowing them to iterate on the same objective in an isolated state.
  • CLI Execution: sypha --fork SHARE_ID
  • Dashboard Implementation: Execute /session fork SHARE_ID within the chat panel.

Operational Best Practices

• Security Integrity: Never paste raw secrets or API keys into the chat interface; utilize environment variables and secret managers.
• Task Granularity: Maintain a high-precision focus within and refine your objectives through iterative follow-up prompts.
• Agile Collaboration: Shared sessions serve as an ideal medium for team reviews, architectural audits, and collaborative problem-solving.