SessionStart: reduce curl call count and standardize flags #20

New issue

Closed

opened 2026-02-24 19:43:56 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-02-24 19:43:56 +00:00

Contributor

Context

PR #16 added project-aware context injection, bringing total sequential curl calls to 7. Each has --connect-timeout 3 --max-time 5.

Issues

Performance risk: Worst case 7 * 3s = 21s if pal-e-docs is unreachable. May exceed Claude Code hook timeout.
Inconsistent curl flags: Old calls use -s, new calls use -sf. Both work but confusing for maintenance.

Suggested fixes

Skip project detection if the first curl (SOPs) fails — pal-e-docs is already unreachable
Reduce --connect-timeout to 2s for project-detection calls
Standardize on -sf across all calls

Discovered in

PR #16 review, round 2

## Context PR #16 added project-aware context injection, bringing total sequential curl calls to 7. Each has `--connect-timeout 3 --max-time 5`. ## Issues 1. **Performance risk**: Worst case 7 * 3s = 21s if pal-e-docs is unreachable. May exceed Claude Code hook timeout. 2. **Inconsistent curl flags**: Old calls use `-s`, new calls use `-sf`. Both work but confusing for maintenance. ## Suggested fixes - Skip project detection if the first curl (SOPs) fails — pal-e-docs is already unreachable - Reduce `--connect-timeout` to 2s for project-detection calls - Standardize on `-sf` across all calls ## Discovered in PR #16 review, round 2