Skip to content

Version Packages - #811

Merged
VeryComplexAndLongName merged 1 commit into
mainfrom
changeset-release/main
Oct 2, 2026
Merged

VeryComplexAndLongName merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@openspec-ui/cli@0.23.0

Minor Changes

  • cc63798: The local LLM agent is built in. local-llm-acp no longer starts an
    external coding-agent that you had to find and install: it is a coding
    agent inside the product, against your OpenAI-compatible server, with
    tools to read, write, replace in a file, list, search and run a command,
    all confined to the change's working directory. Each tool call and its
    result shows in the run. It reads a tool call the model wrote as text
    when the server's parser did not recognise it, as SGLang's hermes
    parser does with Qwen3.6. Turn on
    openspec-ui.localLlm.agent.askBeforeCommands
    (OPENSPEC_UI_LOCAL_LLM_ASK_BEFORE_COMMANDS=1) to allow each command
    yourself.

    The model is optional for local-llm and local-llm-acp: a stage may
    name one, the settings may, and otherwise the server is asked which model
    it serves. A model id may now contain /, as Hugging Face names are
    written.

    Agents can ignore the system proxy: openspec-ui.agents.ignoreSystemProxy
    (OPENSPEC_UI_IGNORE_SYSTEM_PROXY=1). The local LLM agents then connect
    directly, and CLI agents start without the proxy variables and with
    NO_PROXY=*.

    A run that failed inside an ACP agent (any of them, not only
    local-llm-acp) used to say only "Internal error" — the Agent Client
    Protocol's own fixed text for an unhandled exception, with the actual
    cause (an HTTP status, a bad key, a timeout) discarded. It now says that
    cause.

    With openspec-ui.localLlm.agent.askBeforeCommands on, clicking Allow on
    a direct (non-chain) run used to remove the prompt and then go nowhere —
    the answer reached a fresh, unrelated agent instance instead of the one
    actually waiting on it, so the run sat there until cancelled by hand. It
    now reaches the right one.

@openspec-ui/core@0.132.0

Minor Changes

  • cc63798: The local LLM agent is built in. local-llm-acp no longer starts an
    external coding-agent that you had to find and install: it is a coding
    agent inside the product, against your OpenAI-compatible server, with
    tools to read, write, replace in a file, list, search and run a command,
    all confined to the change's working directory. Each tool call and its
    result shows in the run. It reads a tool call the model wrote as text
    when the server's parser did not recognise it, as SGLang's hermes
    parser does with Qwen3.6. Turn on
    openspec-ui.localLlm.agent.askBeforeCommands
    (OPENSPEC_UI_LOCAL_LLM_ASK_BEFORE_COMMANDS=1) to allow each command
    yourself.

    The model is optional for local-llm and local-llm-acp: a stage may
    name one, the settings may, and otherwise the server is asked which model
    it serves. A model id may now contain /, as Hugging Face names are
    written.

    Agents can ignore the system proxy: openspec-ui.agents.ignoreSystemProxy
    (OPENSPEC_UI_IGNORE_SYSTEM_PROXY=1). The local LLM agents then connect
    directly, and CLI agents start without the proxy variables and with
    NO_PROXY=*.

    A run that failed inside an ACP agent (any of them, not only
    local-llm-acp) used to say only "Internal error" — the Agent Client
    Protocol's own fixed text for an unhandled exception, with the actual
    cause (an HTTP status, a bad key, a timeout) discarded. It now says that
    cause.

    With openspec-ui.localLlm.agent.askBeforeCommands on, clicking Allow on
    a direct (non-chain) run used to remove the prompt and then go nowhere —
    the answer reached a fresh, unrelated agent instance instead of the one
    actually waiting on it, so the run sat there until cancelled by hand. It
    now reaches the right one.

openspec-ui-vscode@0.91.0

Minor Changes

  • cc63798: The local LLM agent is built in. local-llm-acp no longer starts an
    external coding-agent that you had to find and install: it is a coding
    agent inside the product, against your OpenAI-compatible server, with
    tools to read, write, replace in a file, list, search and run a command,
    all confined to the change's working directory. Each tool call and its
    result shows in the run. It reads a tool call the model wrote as text
    when the server's parser did not recognise it, as SGLang's hermes
    parser does with Qwen3.6. Turn on
    openspec-ui.localLlm.agent.askBeforeCommands
    (OPENSPEC_UI_LOCAL_LLM_ASK_BEFORE_COMMANDS=1) to allow each command
    yourself.

    The model is optional for local-llm and local-llm-acp: a stage may
    name one, the settings may, and otherwise the server is asked which model
    it serves. A model id may now contain /, as Hugging Face names are
    written.

    Agents can ignore the system proxy: openspec-ui.agents.ignoreSystemProxy
    (OPENSPEC_UI_IGNORE_SYSTEM_PROXY=1). The local LLM agents then connect
    directly, and CLI agents start without the proxy variables and with
    NO_PROXY=*.

    A run that failed inside an ACP agent (any of them, not only
    local-llm-acp) used to say only "Internal error" — the Agent Client
    Protocol's own fixed text for an unhandled exception, with the actual
    cause (an HTTP status, a bad key, a timeout) discarded. It now says that
    cause.

    With openspec-ui.localLlm.agent.askBeforeCommands on, clicking Allow on
    a direct (non-chain) run used to remove the prompt and then go nowhere —
    the answer reached a fresh, unrelated agent instance instead of the one
    actually waiting on it, so the run sat there until cancelled by hand. It
    now reaches the right one.

Patch Changes

  • Updated dependencies [cc63798]
    • @openspec-ui/core@0.132.0
    • @openspec-ui/webui@1.80.0
    • @openspec-ui/server@1.52.0

@openspec-ui/server@1.52.0

Minor Changes

  • cc63798: The local LLM agent is built in. local-llm-acp no longer starts an
    external coding-agent that you had to find and install: it is a coding
    agent inside the product, against your OpenAI-compatible server, with
    tools to read, write, replace in a file, list, search and run a command,
    all confined to the change's working directory. Each tool call and its
    result shows in the run. It reads a tool call the model wrote as text
    when the server's parser did not recognise it, as SGLang's hermes
    parser does with Qwen3.6. Turn on
    openspec-ui.localLlm.agent.askBeforeCommands
    (OPENSPEC_UI_LOCAL_LLM_ASK_BEFORE_COMMANDS=1) to allow each command
    yourself.

    The model is optional for local-llm and local-llm-acp: a stage may
    name one, the settings may, and otherwise the server is asked which model
    it serves. A model id may now contain /, as Hugging Face names are
    written.

    Agents can ignore the system proxy: openspec-ui.agents.ignoreSystemProxy
    (OPENSPEC_UI_IGNORE_SYSTEM_PROXY=1). The local LLM agents then connect
    directly, and CLI agents start without the proxy variables and with
    NO_PROXY=*.

    A run that failed inside an ACP agent (any of them, not only
    local-llm-acp) used to say only "Internal error" — the Agent Client
    Protocol's own fixed text for an unhandled exception, with the actual
    cause (an HTTP status, a bad key, a timeout) discarded. It now says that
    cause.

    With openspec-ui.localLlm.agent.askBeforeCommands on, clicking Allow on
    a direct (non-chain) run used to remove the prompt and then go nowhere —
    the answer reached a fresh, unrelated agent instance instead of the one
    actually waiting on it, so the run sat there until cancelled by hand. It
    now reaches the right one.

Patch Changes

  • Updated dependencies [cc63798]
    • @openspec-ui/core@0.132.0

@openspec-ui/webui@1.80.0

Minor Changes

  • cc63798: The local LLM agent is built in. local-llm-acp no longer starts an
    external coding-agent that you had to find and install: it is a coding
    agent inside the product, against your OpenAI-compatible server, with
    tools to read, write, replace in a file, list, search and run a command,
    all confined to the change's working directory. Each tool call and its
    result shows in the run. It reads a tool call the model wrote as text
    when the server's parser did not recognise it, as SGLang's hermes
    parser does with Qwen3.6. Turn on
    openspec-ui.localLlm.agent.askBeforeCommands
    (OPENSPEC_UI_LOCAL_LLM_ASK_BEFORE_COMMANDS=1) to allow each command
    yourself.

    The model is optional for local-llm and local-llm-acp: a stage may
    name one, the settings may, and otherwise the server is asked which model
    it serves. A model id may now contain /, as Hugging Face names are
    written.

    Agents can ignore the system proxy: openspec-ui.agents.ignoreSystemProxy
    (OPENSPEC_UI_IGNORE_SYSTEM_PROXY=1). The local LLM agents then connect
    directly, and CLI agents start without the proxy variables and with
    NO_PROXY=*.

    A run that failed inside an ACP agent (any of them, not only
    local-llm-acp) used to say only "Internal error" — the Agent Client
    Protocol's own fixed text for an unhandled exception, with the actual
    cause (an HTTP status, a bad key, a timeout) discarded. It now says that
    cause.

    With openspec-ui.localLlm.agent.askBeforeCommands on, clicking Allow on
    a direct (non-chain) run used to remove the prompt and then go nowhere —
    the answer reached a fresh, unrelated agent instance instead of the one
    actually waiting on it, so the run sat there until cancelled by hand. It
    now reaches the right one.

Patch Changes

  • Updated dependencies [cc63798]
    • @openspec-ui/core@0.132.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d7d9e05 to a69217b Compare October 2, 2026 07:50
@VeryComplexAndLongName
VeryComplexAndLongName merged commit 513a5c9 into main Oct 2, 2026
10 checks passed
@VeryComplexAndLongName
VeryComplexAndLongName deleted the changeset-release/main branch October 2, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant