Conversation
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
June 14, 2026 12:02
6c84ab2 to
cd9d5f2
Compare
pd95
marked this pull request as draft
June 14, 2026 15:04
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
June 22, 2026 19:59
cd9d5f2 to
eb608e4
Compare
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
July 8, 2026 12:30
eb608e4 to
cbb9112
Compare
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
August 8, 2026 17:37
cbb9112 to
079c0cf
Compare
This was referenced Aug 8, 2026
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
2 times, most recently
from
August 14, 2026 21:08
12bff25 to
a962d6a
Compare
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
2 times, most recently
from
August 28, 2026 14:46
507808d to
fbeb2c0
Compare
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
August 31, 2026 05:38
fbeb2c0 to
15b572c
Compare
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
September 5, 2026 09:33
15b572c to
3c05eb9
Compare
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
September 14, 2026 06:09
3c05eb9 to
c53c2eb
Compare
pd95
removed this pull request from stack #26
September 14, 2026 18:24
pd95
added this pull request to stack #27
September 14, 2026 18:24
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
pd95
force-pushed
the
feature/responses-namespace-tools-upstream
branch
from
September 18, 2026 12:17
c53c2eb to
3a78148
Compare
Owner
Author
|
Closing because GitHub prevents retargeting this stack-managed PR across the two new v0.34.1 Darwin build layers. A replacement follows on the same head branch. |
Owner
Author
|
Superseded by #32. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The Responses API can group tools under a namespace and represents the
namespace and function name as separate fields. Ollama's internal chat API has
only a flat function name. Passing namespaced tools through without an
injective mapping either loses the namespace on output or makes two children
with the same name ambiguous.
That prevents clients using namespaced tool collections from reliably
round-tripping calls through Ollama's
/v1/responsesendpoint, especially whenstatic tools, deferred tool search, prior history, and streamed output are used
together.
What this changes
(namespace, name)pair to a unique internal name;Dependency and scope
This PR is layered after the MLX build fix but is otherwise a standalone
Responses API change with no model-runtime dependency.
Compare:
fix/mlx-external-reconfigure...feature/responses-namespace-tools-upstream
It transports namespace identity only. It does not add custom/freeform tools,
execute tools, or change cached-token accounting.
Validation
Namespace collision, round-trip, tool-search, history, and literal streaming
and non-streaming middleware tests pass. The integrated Linux test/lint/build
and Darwin MLX build gates also pass.
Refresh and AI assistance
Adapted onto Ollama
v0.34.0; headc53c2ebe046e20eec8271b50ab727234ddab1efa. Codex materially assisted theimplementation review, tests, refresh validation, and this PR description.