feat(daily-summary): add atuin shell history as signal source - #914
Conversation
Supplements memsearch memory with filtered atuin history for the day. Deduplicates retry sequences and drops bare navigational commands. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe changes add ChangesSandbox command exclusions
Daily summary workflow
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
There was a problem hiding this comment.
Code Review
This pull request adds "atuin *" to the sandbox excluded commands in Claude settings and updates the daily-summary skill to load and merge shell history using atuin search when memory logs are missing. Feedback was provided to include the {exit} status in the atuin search format string, enabling the agent to correctly identify and filter successful command retries as specified in the instructions.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| atuin search --after "<date> 00:00:00" --before "<date+1> 00:00:00" \ | ||
| --format "{time} {directory} {command}" --limit 2000 2>/dev/null |
There was a problem hiding this comment.
In step 3, the instructions ask to "keep only the last successful variant when a command was retried". However, the atuin search command format only requests {time} {directory} {command}. Without the exit status ({exit}), the agent won't be able to distinguish between successful and failed commands to perform this filtering.
Including {exit} in the --format string will provide the necessary exit code context.
| atuin search --after "<date> 00:00:00" --before "<date+1> 00:00:00" \ | |
| --format "{time} {directory} {command}" --limit 2000 2>/dev/null | |
| atuin search --after "<date> 00:00:00" --before "<date+1> 00:00:00" \ | |
| --format "{time} {directory} {exit} {command}" --limit 2000 2>/dev/null |

Summary
atuin *from Claude Code permission promptsTest plan
/daily-summary <date>and verify atuin commands appear in output🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Bug Fixes
atuincommands to the sandbox’s excluded command list for safer execution.