Commit Graph

4 Commits

  • feat: add maxDelayMs setting to cap server-requested retry delays
    When a provider (e.g., Google Gemini CLI) requests a retry delay longer
    than maxDelayMs (default: 60s), the request fails immediately with an
    informative error instead of waiting silently for hours.
    
    The error is then handled by agent-level auto-retry, which shows the
    delay to the user and allows aborting with Escape.
    
    - Add maxRetryDelayMs to StreamOptions (packages/ai)
    - Add maxRetryDelayMs to AgentOptions (packages/agent)
    - Add retry.maxDelayMs to settings (packages/coding-agent)
    - Update _isRetryableError to match 'retry delay' errors
    
    fixes #1123
  • fix(coding-agent): add force exclude pattern and fix config toggle persistence
    - Add `-path` force-exclude pattern (exact path match, highest precedence)
    - Change `+path` force-include to exact path match (no glob)
    - Manifest-excluded resources are now hidden from config (not toggleable)
    - Config toggle uses `+` to enable and `-` to disable
    - Settings paths resolve relative to settings.json location:
      - Global: relative to ~/.pi/agent
      - Project: relative to .pi
    - Add baseDir to PathMetadata for proper relative path computation
    - Update tests for new base directory and pattern behavior
    
    fixes #951
  • docs(coding-agent): update README-NEW.md, tui.md, add new docs
    - README-NEW.md: add environment variables, philosophy extras (no built-in to-dos, no background bash), session ID support, pi config command, plain git URLs, version pinning
    - tui.md: fix hooks->extensions terminology, update Component interface (invalidate required, add wantsKeyRelease)
    - Add new docs: settings.md, development.md, json.md
    - Add screenshots: tree-view.png, doom-extension.png