session-flow: remove a delivered absence's away state so idle hook cost returns to the cheap path
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- performance, tooling
Research direction
Start with the session-flow away hooks and the deliver and end paths that write the away/<session> state under the plugin data dir. Check whether the Python startup cost only appears once that directory exists. Done means a delivered absence leaves no away/<session> directory (or one within the stated retention), the report stays readable as long as that retention allows, tests cover the cleanup, and the idle hook timing is recorded. Linked PR #17396 is already open, so coordinate there first.
Written by the indexing model from the issue text.
Description
Problem
session-flow's always-registered away hooks cost about 0.02 s per prompt and turn end when no away state exists (Python never starts). Once any away/ directory exists under the plugin data dir, the cost is about 0.09 s. A finished absence's state stays in place, so every later session pays the higher cost.
Done looks like
deliver(orend) removes a finished absence's state, or keeps it for a stated bounded retention.- After a delivered absence, no
away/<session>directory remains (or only within the retention bound). - Measured idle hook cost in a session with no active absence is back to about 0.02 s, with the measurement recorded in the PR.
- Tests cover the cleanup, and the report remains readable after delivery for as long as the retention says.
Refs: #17337
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 942
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from melodic-software/claude-code-plugins
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melodic-software/claude-code-plugins#17374 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
melodic-software/claude-code-plugins#17364 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
melodic-software/claude-code-plugins#17039 · 7 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#16931 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
melodic-software/claude-code-plugins#15498 · 3 comments ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
application-issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Installomator/Installomator#3657 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nekko-labs/nekko-agent#2998 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
kenzok8/openwrt-honk#35 ·
Maintainers usually reply within 1 day
-
bug severity:medium triage:confirmed triage:in-progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cotal-AI/Cotal#7795 · 1 comment ·
Maintainers usually reply within 1 day