Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: jackwener/OpenCLI
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.6.6
Choose a base ref
...
head repository: jackwener/OpenCLI
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.6.7
Choose a head ref
  • 3 commits
  • 10 files changed
  • 2 contributors

Commits on Apr 5, 2026

  1. fix: avoid inserting completion config inside multi-line shell comman… 

    …ds (#796)

* fix: avoid inserting completion config inside multi-line shell commands

The postinstall zshrc insertion logic splits backslash-continued blocks
(e.g. zinit stanzas) when it finds a compinit match inside them, which
breaks the user's shell config. Walk backward past continuation lines
so the insertion lands before the entire logical command.

* fix: append zsh completion to end of .zshrc instead of splicing

Replace the fragile compinit-searching splice logic with a simple
append, matching the strategy already used for bash. This avoids
breaking multi-line commands (e.g. zinit blocks with zicompinit).

Still detects existing compinit to avoid adding a duplicate call.

* fix: stop modifying shell rc files in postinstall

Replace the fragile .zshrc/.bashrc modification logic with a safer
approach: only write completion files and print setup instructions.

The previous approach tried to parse and splice into rc files, which
broke multi-line shell commands (e.g. zinit blocks with backslash
continuations matching /compinit/). Instead of attempting to fix the
parser, remove rc modification entirely — this matches the approach
used by rustup, homebrew, and other CLI tools.

Closes #788

---------

Co-authored-by: jackwener <jakevingoo@gmail.com>
    @kaichen @jackwener
    kaichen and jackwener authored Apr 5, 2026
    Configuration menu
    Copy the full SHA
    97a547c View commit details
    Browse the repository at this point in the history

  2. feat: structured diagnostic output for AI-driven adapter repair (#802) 

    * feat: add structured diagnostic output for AI-driven adapter repair

When OPENCLI_DIAGNOSTIC=1 is set, failed commands emit a RepairContext
JSON to stderr containing the error, adapter source, and browser state
(DOM snapshot, network requests, console errors). AI Agents consume
this to diagnose and fix adapters when websites change.

Also adds the opencli-repair skill guide for AI Agents.

* fix: correct e2e test binary path to dist/src/main.js

The e2e helpers pointed to dist/main.js but the actual build output
is at dist/src/main.js (matching package.json "main" field). This
caused all e2e-headed tests to fail with "Cannot find module".

* fix: correct dist/main.js path in autoresearch scripts

* fix: emit diagnostic for pre-session browser failures

When browser connection fails before the session callback runs
(e.g., BrowserConnectError), the inner diagnostic catch never fires.
Use a flag to ensure the outer catch emits diagnostic as a fallback.

* test: tolerate unavailable Bloomberg RSS feeds in e2e

* test: skip flaky bloomberg businessweek e2e test

The Bloomberg Businessweek RSS feed is intermittently unavailable,
causing CI failures unrelated to code changes.

* revert: restore bloomberg businessweek e2e coverage
    @jackwener
    jackwener authored Apr 5, 2026
    Configuration menu
    Copy the full SHA
    664a971 View commit details
    Browse the repository at this point in the history

  3. chore: bump version to 1.6.7

    @jackwener
    jackwener authored Apr 5, 2026
    Configuration menu
    Copy the full SHA
    d51338c View commit details
    Browse the repository at this point in the history
Loading