What evloghq/evlog shipped
Written by FoxPlug from public releases; not affiliated with Evlog. An automatic summary of the public release, pull request and commit data of github.com/evloghq/evlog. Evlog did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 14, 2026
What shipped
- Evi can now work on repositories that use evlog, not just evlog itself, by carrying three published skills for log analysis and patterns. Pull request #726
- Added git__checkout to clone any installed repository into the sandbox at a specific branch or commit. Pull request #723
- Technical replies on GitHub now include collapsed ELI5 explanations for clarity, while Slack stays conversational. Pull request #727
- Evi repository configuration is now centralized in one module, defaulting to evloghq/evlog but readable from environment and channel state. Pull request #722
- Upgraded eve dependency to 0.63.0 to match the eve-extension version requirement. Pull request #718
Why it matters
Evi can now work across repositories using evlog and access their code directly in the sandbox. The centralized repository configuration makes Evi more flexible for different deployment contexts. These changes expand Evi's utility beyond analyzing evlog itself.
Changelog entry
- Evi can now work on repositories using evlog with three published skills for log analysis and pattern review Pull request #726
- Added git__checkout to clone installed repositories into sandbox at specified branches or commits Pull request #723
- Technical replies on GitHub now include optional collapsed ELI5 explanations Pull request #727
- Centralized repository resolution via EVI_REPOSITORY environment variable and channel state Pull request #722
- Upgraded eve to 0.63.0 Pull request #718
Evi now works on any repository using evlog, not just evlog itself. Clone code directly into the sandbox and apply logging patterns across your projects.
This week Evi expanded beyond analyzing evlog to work on any repository that uses it. You can now carry published logging skills into new projects, clone repositories directly into the sandbox, and centralize repository configuration. Technical replies gain collapsible explanations for clarity.