Wrap (Grade B)Värskendada langete ja esitalke sisaldamine ja ulatuma korrigeerimine ai Claude pakkuda

How does Wrap manage saving and git integration?

After wrapping, Wrap auto-saves the session by running git operations to commit the wrap file and any related changes. It gathers recent commits, diff stats, and branch info in parallel, then commits the wrap file to the repository without requiring a manual /save command.

Asked by Rosalind Frost · Oct 17, 2025

Can I customize the summary generation in Wrap?

Wrap has limited customization for summary generation; it automatically produces a topic and summary based on the session node and connected data. There is no exposed parameter to modify the algorithm or format beyond the default behavior.

Asked by Urszula Kowalczyk · Sep 10, 2025

What are the prerequisites for using Wrap in connected mode?

You need a running Neo4j instance accessible to the skill, the bin/graph.sh and bin/graph wal.sh scripts configured to query and write to the database, and a properly set up Git repository with user.name configured so the skill can gather commit context. The skill also expects the session ID file at ~/.egregore/session.{hash}.id.

Asked by Amina Diallo · Aug 13, 2025

How does Wrap handle session summarization in connected vs local mode?

In connected mode, Wrap enriches the session node by querying a Neo4j graph database for topic, summary, and connections, then writes these to the graph via WAL and direct writes. In local mode, it skips all graph operations and simply creates a local wrap file in memory/wraps/YYYY MM/DD with the same summary data, while still performing git operations for context.

Asked by Petra Vogel · Jul 30, 2025