record-session

To record a git coding session into a local journal, this tool captures your latest commit hash and a brief summary, writing them into .trellis/workspace journal files to preserve coding context for future AI-assisted work.

A session journal preserves coding context by storing completed session summaries and commit hashes in local .trellis metadata, enabling future AI agents to access persistent knowledge and recall previous development work.

You should archive session data using .trellis workspace files immediately after finishing human testing and committing your code, ensuring the recorded session context accurately reflects the completed state.

Yes, you need to run a git commit before recording a coding session, because this tool references your latest commit hash to anchor the session summary and ensure the archived data matches the tested state.

The best way to maintain persistent context across coding sessions is using local .trellis metadata to capture session summaries and developer index updates, allowing future AI-assisted work to recall previous tasks seamlessly.

Yes, you can update developer index files automatically after a coding session, as this tool maintains session-level summaries and updates index files within the .trellis workspace to support future reference.