tessera

Use tessera to remember this repository’s module structure, key service entry points, and recent change history. Later, when I ask where a feature lives, answer from memory first and read files only if necessary.

The tool stores project structure and change context so later feature and file lookup is faster.

Record today’s investigation of the login failure, attempted fixes, and related files into tessera. At the start of the next session, summarize known findings and remaining tasks first.

The tool preserves debugging history so a new session can resume analysis and fixes immediately.

Build semantic memory for this codebase, including core classes, dependencies, and common action history. Before suggesting a refactor, use tessera’s memory to estimate impact and then decide which files to read.

It narrows analysis with persistent memory first, then reads only targeted files for better efficiency.