Repository navigation
feat: the trigger test runs Qwen Code, with a model on any OpenAI-compatible server - #105
Merged
Merged
Conversation
…patible server Signed-off-by: alkhatibdev <me@alkhatib.dev>
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.
The trigger test runs Qwen Code
The trigger test measured one AI assistant, Claude Code. This pull request adds Qwen Code 0.27.4,
talking to any server with an OpenAI-compatible API, so the same held-out tasks can show whether
a model on your own machine looks the law up before it touches personal data.
What changes
--client qwen-code, with--modeland--base-urlnaming the model and the server thatholds it, and the server's key in
OPENAI_API_KEY.--samplingis sent with every request,and
--context-windowtells Qwen Code how much context the server gives the model. Both arekept with the batch, and a resumed batch has to match them.
same Larder stage. Claude Code's two scripts move to
container/claude-code/, unchanged, andQwen Code's sit in
container/qwen-code/.qwen mcp addwrites, and nothing that reports usage, fetches a model catalogue or updatesQwen Code.
edit,write_file,notebook_edit), and its turn limit, which it prints on stderr with no final event. It keepsMCP tools out of the prompt until the model looks one up, so a search can arrive through its
tool_calltool, and counts the same.--stop-at-editends a run at its first edit, when whether it searched before editing isknown, which keeps runs short on a slow model.
--writerefuses such a batch, and any batchthat is not Claude Code's, since
evals/results/trigger.jsonis Claude Code's number.Tests
tool_callis a call, and looking a tool up is not.tool_callresolves the way Qwen Code resolves it.--stop-at-editends a run at its first edit, and without it the run goes on to its search.--writerefuses a batch stopped at its first edit and a Qwen Code batch.Each new behaviour, taken out in turn, fails its test.
Checked by running it
numbers with it, and
--rereadchanges no field of any of their outcomes.with
--stop-at-edit, all scored: the question searched first and its answer came back, withone row in the query log for its one call, and the two coding tasks edited without searching.
Each run took 8 to 33 seconds, and the batch recorded the server, the sampling and the
context window.
mainbuilds: the same Claude Code, user, environment,global packages, app files, Larder history (the same three commits) and
node_modules, andits two scripts byte for byte.
prepare-profile.sh mcp-onlyruns in it. No Claude Code run wasmade with this change.