docdex

{"query_id": "q1", "query": "how to disable web cache for a query", "agent": "codex-deputy", "elapsed_s": 0.016, "ok": true, "response": {"results": {"local": {"score": 0.68421024, "path": "docs/symbols_store.md", "summary": "Symbols store (optional code intelligence) — Docdex can optionally extract per-file **symbols** during indexing and persist them in a repo-scoped symbols store. Downstream features (e.g. MCP clients) can query this store via a documented interface. This document describes: How t…"}}}} {"query_id": "q1", "query": "how to disable web cache for a query", "agent": "codex-architect", "elapsed_s": 0.013, "ok": true, "response": {"results": {"local": {"score": 0.68421024, "path": "docs/symbols_store.md", "summary": "Symbols store (optional code intelligence) — Docdex can optionally extract per-file **symbols** during indexing and persist them in a repo-scoped symbols store. Downstream features (e.g. MCP clients) can query this store via a documented interface. This document describes: How t…"}}}} {"query_id": "q1", "query": "how to disable web cache for a query", "agent": "gemini-stable", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.68421024, "path": "docs/symbols_store.md", "summary": "Symbols store (optional code intelligence) — Docdex can optionally extract per-file **symbols** during indexing and persist them in a repo-scoped symbols store. Downstream features (e.g. MCP clients) can query this store via a documented interface. This document describes: How t…"}}}} {"query_id": "q1", "query": "how to disable web cache for a query", "agent": "devstral-local", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.68421024, "path": "docs/symbols_store.md", "summary": "Symbols store (optional code intelligence) — Docdex can optionally extract per-file **symbols** during indexing and persist them in a repo-scoped symbols store. Downstream features (e.g. MCP clients) can query this store via a documented interface. This document describes: How t…"}}}} {"query_id": "q1", "query": "how to disable web cache for a query", "agent": "gpt-oss-qa", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.68421024, "path": "docs/symbols_store.md", "summary": "Symbols store (optional code intelligence) — Docdex can optionally extract per-file **symbols** during indexing and persist them in a repo-scoped symbols store. Downstream features (e.g. MCP clients) can query this store via a documented interface. This document describes: How t…"}}}} {"query_id": "q2", "query": "where is the mcoda registry reader implemented", "agent": "codex-deputy", "elapsed_s": 0.011, "ok": true, "response": {"results": {"web": {"score": 1.0, "url": "", "ai_digested_content": "Computers with embedded readers will try to pass the SIM card as an RFID card. This happens because of their close proximity to each other within the device itself and can cause a number of odd, inappropriate behaviors by the MFA software. Some of these behaviors can look like:Computer beeping as if a card has been scanned at loginThe same username appears to attempt to \"badge-in\" every timeUsers frequently receive \"This card is not registered\" when that user is known to be enrolledThe same username appears on multiple computers that they have never touchedThe computer beeps as if a card has been read then locks itselfBeing unable to enroll a contactless card; seeing a value appear in the card data during an enrollment before you even scan your cardThe following instructions will demonstrate an example on how to confirm the behavior, followed by creating a RapidIdentity MFA-specific registry value that tells the software to ignore the smart card reader.These steps cannot be generalized into a single .REG file as the computers' UICC values will are unique to each computer.Validating The BehaviorOpen the Rapid Identity MFA desktop application.Once open, click onEnrollment Wizardat the bottom.Select theProximity Cardoption.The \"Serial Number\" will quickly populate with a long, overflowing string of hexadecimal values.⚠️ Do not finish the card enrollment process at this step.Be sure to take note of the user assigned to this value. They will need to re-enroll their proximity card after this fix because their card was assigned to the SIM card value. You will also need to be sure and clear the client computer's cached credentials (and any others that might have experienced this or been affected by) by following themanual removal instructionsor downloading ourUser Removal Tool.Open an elevated command prompt.Run the command:certutil -scinfoYou'll notice that the hex value fromStep 3will appear under one of your computer's readers - typically theMicrosoft UICC ISO Reader. This reader is your computer's unique smart card reader value that our software will need instruction to ignore.Method 1 (Manually) - Ignoring The ReaderCopy the reader name (including the single number at the end of the string, in this example it's the zero).Open your regedit and navigate to HKLM\\Software\\Foray.Create a new multi-string sub-key:\"SCIgnoreReaders\" MULTI_SZ = <card reader name fromStep 1>Restart the computer.Method 2 (Automated) - PowerShell ScriptThe following PowerShell script can be run to automatically perform the same actions as the method above, and will account for all UICC values that may be present on your computer(s). Copy/paste the code below. If you receive any errors when running, be sure you are running with elevated rights."}}}} {"query_id": "q2", "query": "where is the mcoda registry reader implemented", "agent": "codex-architect", "elapsed_s": 0.012, "ok": true, "response": {"results": {"web": {"score": 1.0, "url": "", "ai_digested_content": "Computers with embedded readers will try to pass the SIM card as an RFID card. This happens because of their close proximity to each other within the device itself and can cause a number of odd, inappropriate behaviors by the MFA software. Some of these behaviors can look like:Computer beeping as if a card has been scanned at loginThe same username appears to attempt to \"badge-in\" every timeUsers frequently receive \"This card is not registered\" when that user is known to be enrolledThe same username appears on multiple computers that they have never touchedThe computer beeps as if a card has been read then locks itselfBeing unable to enroll a contactless card; seeing a value appear in the card data during an enrollment before you even scan your cardThe following instructions will demonstrate an example on how to confirm the behavior, followed by creating a RapidIdentity MFA-specific registry value that tells the software to ignore the smart card reader.These steps cannot be generalized into a single .REG file as the computers' UICC values will are unique to each computer.Validating The BehaviorOpen the Rapid Identity MFA desktop application.Once open, click onEnrollment Wizardat the bottom.Select theProximity Cardoption.The \"Serial Number\" will quickly populate with a long, overflowing string of hexadecimal values.⚠️ Do not finish the card enrollment process at this step.Be sure to take note of the user assigned to this value. They will need to re-enroll their proximity card after this fix because their card was assigned to the SIM card value. You will also need to be sure and clear the client computer's cached credentials (and any others that might have experienced this or been affected by) by following themanual removal instructionsor downloading ourUser Removal Tool.Open an elevated command prompt.Run the command:certutil -scinfoYou'll notice that the hex value fromStep 3will appear under one of your computer's readers - typically theMicrosoft UICC ISO Reader. This reader is your computer's unique smart card reader value that our software will need instruction to ignore.Method 1 (Manually) - Ignoring The ReaderCopy the reader name (including the single number at the end of the string, in this example it's the zero).Open your regedit and navigate to HKLM\\Software\\Foray.Create a new multi-string sub-key:\"SCIgnoreReaders\" MULTI_SZ = <card reader name fromStep 1>Restart the computer.Method 2 (Automated) - PowerShell ScriptThe following PowerShell script can be run to automatically perform the same actions as the method above, and will account for all UICC values that may be present on your computer(s). Copy/paste the code below. If you receive any errors when running, be sure you are running with elevated rights."}}}} {"query_id": "q2", "query": "where is the mcoda registry reader implemented", "agent": "gemini-stable", "elapsed_s": 70.73, "ok": true, "response": {"results": {"web": {"score": 0.2, "url": "https://mfa.rapididentity.com/docs/scignorereaders-for-internal-readers", "ai_digested_content": "Computers with embedded readers will try to pass the SIM card as an RFID card. This happens because of their close proximity to each other within the device itself and can cause a number of odd, inappropriate behaviors by the MFA software. Some of these behaviors can look like:Computer beeping as if a card has been scanned at loginThe same username appears to attempt to \"badge-in\" every timeUsers frequently receive \"This card is not registered\" when that user is known to be enrolledThe same username appears on multiple computers that they have never touchedThe computer beeps as if a card has been read then locks itselfBeing unable to enroll a contactless card; seeing a value appear in the card data during an enrollment before you even scan your cardThe following instructions will demonstrate an example on how to confirm the behavior, followed by creating a RapidIdentity MFA-specific registry value that tells the software to ignore the smart card reader.These steps cannot be generalized into a single .REG file as the computers' UICC values will are unique to each computer.Validating The BehaviorOpen the Rapid Identity MFA desktop application.Once open, click onEnrollment Wizardat the bottom.Select theProximity Cardoption.The \"Serial Number\" will quickly populate with a long, overflowing string of hexadecimal values.⚠️ Do not finish the card enrollment process at this step.Be sure to take note of the user assigned to this value. They will need to re-enroll their proximity card after this fix because their card was assigned to the SIM card value. You will also need to be sure and clear the client computer's cached credentials (and any others that might have experienced this or been affected by) by following themanual removal instructionsor downloading ourUser Removal Tool.Open an elevated command prompt.Run the command:certutil -scinfoYou'll notice that the hex value fromStep 3will appear under one of your computer's readers - typically theMicrosoft UICC ISO Reader. This reader is your computer's unique smart card reader value that our software will need instruction to ignore.Method 1 (Manually) - Ignoring The ReaderCopy the reader name (including the single number at the end of the string, in this example it's the zero).Open your regedit and navigate to HKLM\\Software\\Foray.Create a new multi-string sub-key:\"SCIgnoreReaders\" MULTI_SZ = <card reader name fromStep 1>Restart the computer.Method 2 (Automated) - PowerShell ScriptThe following PowerShell script can be run to automatically perform the same actions as the method above, and will account for all UICC values that may be present on your computer(s). Copy/paste the code below. If you receive any errors when running, be sure you are running with elevated rights."}}}} {"query_id": "q2", "query": "where is the mcoda registry reader implemented", "agent": "devstral-local", "elapsed_s": 19.568, "ok": true, "response": {"results": {"web": {"score": 0.2, "url": "https://mfa.rapididentity.com/docs/scignorereaders-for-internal-readers", "ai_digested_content": "Computers with embedded readers will try to pass the SIM card as an RFID card. This happens because of their close proximity to each other within the device itself and can cause a number of odd, inappropriate behaviors by the MFA software. Some of these behaviors can look like:Computer beeping as if a card has been scanned at loginThe same username appears to attempt to \"badge-in\" every timeUsers frequently receive \"This card is not registered\" when that user is known to be enrolledThe same username appears on multiple computers that they have never touchedThe computer beeps as if a card has been read then locks itselfBeing unable to enroll a contactless card; seeing a value appear in the card data during an enrollment before you even scan your cardThe following instructions will demonstrate an example on how to confirm the behavior, followed by creating a RapidIdentity MFA-specific registry value that tells the software to ignore the smart card reader.These steps cannot be generalized into a single .REG file as the computers' UICC values will are unique to each computer.Validating The BehaviorOpen the Rapid Identity MFA desktop application.Once open, click onEnrollment Wizardat the bottom.Select theProximity Cardoption.The \"Serial Number\" will quickly populate with a long, overflowing string of hexadecimal values.⚠️ Do not finish the card enrollment process at this step.Be sure to take note of the user assigned to this value. They will need to re-enroll their proximity card after this fix because their card was assigned to the SIM card value. You will also need to be sure and clear the client computer's cached credentials (and any others that might have experienced this or been affected by) by following themanual removal instructionsor downloading ourUser Removal Tool.Open an elevated command prompt.Run the command:certutil -scinfoYou'll notice that the hex value fromStep 3will appear under one of your computer's readers - typically theMicrosoft UICC ISO Reader. This reader is your computer's unique smart card reader value that our software will need instruction to ignore.Method 1 (Manually) - Ignoring The ReaderCopy the reader name (including the single number at the end of the string, in this example it's the zero).Open your regedit and navigate to HKLM\\Software\\Foray.Create a new multi-string sub-key:\"SCIgnoreReaders\" MULTI_SZ = <card reader name fromStep 1>Restart the computer.Method 2 (Automated) - PowerShell ScriptThe following PowerShell script can be run to automatically perform the same actions as the method above, and will account for all UICC values that may be present on your computer(s). Copy/paste the code below. If you receive any errors when running, be sure you are running with elevated rights."}}}} {"query_id": "q2", "query": "where is the mcoda registry reader implemented", "agent": "gpt-oss-qa", "elapsed_s": 19.24, "ok": true, "response": {"results": {"web": {"score": 0.2, "url": "https://mfa.rapididentity.com/docs/scignorereaders-for-internal-readers", "ai_digested_content": "Computers with embedded readers will try to pass the SIM card as an RFID card. This happens because of their close proximity to each other within the device itself and can cause a number of odd, inappropriate behaviors by the MFA software. Some of these behaviors can look like:Computer beeping as if a card has been scanned at loginThe same username appears to attempt to \"badge-in\" every timeUsers frequently receive \"This card is not registered\" when that user is known to be enrolledThe same username appears on multiple computers that they have never touchedThe computer beeps as if a card has been read then locks itselfBeing unable to enroll a contactless card; seeing a value appear in the card data during an enrollment before you even scan your cardThe following instructions will demonstrate an example on how to confirm the behavior, followed by creating a RapidIdentity MFA-specific registry value that tells the software to ignore the smart card reader.These steps cannot be generalized into a single .REG file as the computers' UICC values will are unique to each computer.Validating The BehaviorOpen the Rapid Identity MFA desktop application.Once open, click onEnrollment Wizardat the bottom.Select theProximity Cardoption.The \"Serial Number\" will quickly populate with a long, overflowing string of hexadecimal values.⚠️ Do not finish the card enrollment process at this step.Be sure to take note of the user assigned to this value. They will need to re-enroll their proximity card after this fix because their card was assigned to the SIM card value. You will also need to be sure and clear the client computer's cached credentials (and any others that might have experienced this or been affected by) by following themanual removal instructionsor downloading ourUser Removal Tool.Open an elevated command prompt.Run the command:certutil -scinfoYou'll notice that the hex value fromStep 3will appear under one of your computer's readers - typically theMicrosoft UICC ISO Reader. This reader is your computer's unique smart card reader value that our software will need instruction to ignore.Method 1 (Manually) - Ignoring The ReaderCopy the reader name (including the single number at the end of the string, in this example it's the zero).Open your regedit and navigate to HKLM\\Software\\Foray.Create a new multi-string sub-key:\"SCIgnoreReaders\" MULTI_SZ = <card reader name fromStep 1>Restart the computer.Method 2 (Automated) - PowerShell ScriptThe following PowerShell script can be run to automatically perform the same actions as the method above, and will account for all UICC values that may be present on your computer(s). Copy/paste the code below. If you receive any errors when running, be sure you are running with elevated rights."}}}} {"query_id": "q3", "query": "how does docdexd choose web discovery", "agent": "codex-deputy", "elapsed_s": 0.013, "ok": true, "response": {"results": {"local": {"score": 0.662249, "path": "docs/ops/web_discovery_ddg_audit.md", "summary": "Web Discovery + DDG HTML Audit — Task: bck-05-us-07-t14 Scope Audit current web discovery implementation and DDG HTML touchpoints (requests, parsing, dedupe, rate limiting/backoff) across CLI/HTTP/MCP surfaces."}}}} {"query_id": "q3", "query": "how does docdexd choose web discovery", "agent": "codex-architect", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.662249, "path": "docs/ops/web_discovery_ddg_audit.md", "summary": "Web Discovery + DDG HTML Audit — Task: bck-05-us-07-t14 Scope Audit current web discovery implementation and DDG HTML touchpoints (requests, parsing, dedupe, rate limiting/backoff) across CLI/HTTP/MCP surfaces."}}}} {"query_id": "q3", "query": "how does docdexd choose web discovery", "agent": "gemini-stable", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.662249, "path": "docs/ops/web_discovery_ddg_audit.md", "summary": "Web Discovery + DDG HTML Audit — Task: bck-05-us-07-t14 Scope Audit current web discovery implementation and DDG HTML touchpoints (requests, parsing, dedupe, rate limiting/backoff) across CLI/HTTP/MCP surfaces."}}}} {"query_id": "q3", "query": "how does docdexd choose web discovery", "agent": "devstral-local", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.662249, "path": "docs/ops/web_discovery_ddg_audit.md", "summary": "Web Discovery + DDG HTML Audit — Task: bck-05-us-07-t14 Scope Audit current web discovery implementation and DDG HTML touchpoints (requests, parsing, dedupe, rate limiting/backoff) across CLI/HTTP/MCP surfaces."}}}} {"query_id": "q3", "query": "how does docdexd choose web discovery", "agent": "gpt-oss-qa", "elapsed_s": 0.013, "ok": true, "response": {"results": {"local": {"score": 0.662249, "path": "docs/ops/web_discovery_ddg_audit.md", "summary": "Web Discovery + DDG HTML Audit — Task: bck-05-us-07-t14 Scope Audit current web discovery implementation and DDG HTML touchpoints (requests, parsing, dedupe, rate limiting/backoff) across CLI/HTTP/MCP surfaces."}}}} {"query_id": "q4", "query": "where is llm agent option threaded through chat", "agent": "codex-deputy", "elapsed_s": 0.013, "ok": true, "response": {"results": {"local": {"score": 0.58321846, "path": ".mcoda/handoffs/gateway-33a2fa5a-9dba-4109-8050-14bab6419ee3.md", "summary": "Gateway Handoff — Job: work-on-tasks Gateway agent: codex-architect Chosen agent: glm-worker Summary Implement an OpenAI Chat Completions response adapter that returns the required envelope and choices fields, preserving compatibility with existing OpenAI clients and avoiding da…"}}}} {"query_id": "q4", "query": "where is llm agent option threaded through chat", "agent": "codex-architect", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.58321846, "path": ".mcoda/handoffs/gateway-33a2fa5a-9dba-4109-8050-14bab6419ee3.md", "summary": "Gateway Handoff — Job: work-on-tasks Gateway agent: codex-architect Chosen agent: glm-worker Summary Implement an OpenAI Chat Completions response adapter that returns the required envelope and choices fields, preserving compatibility with existing OpenAI clients and avoiding da…"}}}} {"query_id": "q4", "query": "where is llm agent option threaded through chat", "agent": "gemini-stable", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.58321846, "path": ".mcoda/handoffs/gateway-33a2fa5a-9dba-4109-8050-14bab6419ee3.md", "summary": "Gateway Handoff — Job: work-on-tasks Gateway agent: codex-architect Chosen agent: glm-worker Summary Implement an OpenAI Chat Completions response adapter that returns the required envelope and choices fields, preserving compatibility with existing OpenAI clients and avoiding da…"}}}} {"query_id": "q4", "query": "where is llm agent option threaded through chat", "agent": "devstral-local", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.58321846, "path": ".mcoda/handoffs/gateway-33a2fa5a-9dba-4109-8050-14bab6419ee3.md", "summary": "Gateway Handoff — Job: work-on-tasks Gateway agent: codex-architect Chosen agent: glm-worker Summary Implement an OpenAI Chat Completions response adapter that returns the required envelope and choices fields, preserving compatibility with existing OpenAI clients and avoiding da…"}}}} {"query_id": "q4", "query": "where is llm agent option threaded through chat", "agent": "gpt-oss-qa", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.58321846, "path": ".mcoda/handoffs/gateway-33a2fa5a-9dba-4109-8050-14bab6419ee3.md", "summary": "Gateway Handoff — Job: work-on-tasks Gateway agent: codex-architect Chosen agent: glm-worker Summary Implement an OpenAI Chat Completions response adapter that returns the required envelope and choices fields, preserving compatibility with existing OpenAI clients and avoiding da…"}}}} {"query_id": "q5", "query": "function that builds query category prompt", "agent": "codex-deputy", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.6612192, "path": "AGENT_PROMPT.md", "summary": "Docdex — Agent Prompt — You are interacting with Docdex, a local documentation indexer/search daemon. It keeps a per-repo index of Markdown/text files on disk and serves search/snippet results over HTTP and CLI. No external services are used; all data stays local. What Docdex do…"}}}} {"query_id": "q5", "query": "function that builds query category prompt", "agent": "codex-architect", "elapsed_s": 0.011, "ok": true, "response": {"results": {"local": {"score": 0.6612192, "path": "AGENT_PROMPT.md", "summary": "Docdex — Agent Prompt — You are interacting with Docdex, a local documentation indexer/search daemon. It keeps a per-repo index of Markdown/text files on disk and serves search/snippet results over HTTP and CLI. No external services are used; all data stays local. What Docdex do…"}}}} {"query_id": "q5", "query": "function that builds query category prompt", "agent": "gemini-stable", "elapsed_s": 0.013, "ok": true, "response": {"results": {"local": {"score": 0.6612192, "path": "AGENT_PROMPT.md", "summary": "Docdex — Agent Prompt — You are interacting with Docdex, a local documentation indexer/search daemon. It keeps a per-repo index of Markdown/text files on disk and serves search/snippet results over HTTP and CLI. No external services are used; all data stays local. What Docdex do…"}}}} {"query_id": "q5", "query": "function that builds query category prompt", "agent": "devstral-local", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.6612192, "path": "AGENT_PROMPT.md", "summary": "Docdex — Agent Prompt — You are interacting with Docdex, a local documentation indexer/search daemon. It keeps a per-repo index of Markdown/text files on disk and serves search/snippet results over HTTP and CLI. No external services are used; all data stays local. What Docdex do…"}}}} {"query_id": "q5", "query": "function that builds query category prompt", "agent": "gpt-oss-qa", "elapsed_s": 0.012, "ok": true, "response": {"results": {"local": {"score": 0.6612192, "path": "AGENT_PROMPT.md", "summary": "Docdex — Agent Prompt — You are interacting with Docdex, a local documentation indexer/search daemon. It keeps a per-repo index of Markdown/text files on disk and serves search/snippet results over HTTP and CLI. No external services are used; all data stays local. What Docdex do…"}}}} {"query_id": "q6", "query": "java oauth2 code sample", "agent": "codex-deputy", "elapsed_s": 37.452, "ok": true, "response": {"results": {"web": {"score": 0.511, "url": "https://www.codejava.net/rest-api/authorization-server-oauth-2-persistent-credentials", "ai_digested_content": "Spring Data JPA test creates OAuth2 Client entities, encodes secrets with BCryptPasswordEncoder, saves them via ClientRepository, and queries a client by its ID."}}}} {"query_id": "q6", "query": "java oauth2 code sample", "agent": "codex-architect", "elapsed_s": 20.659, "ok": true, "response": {"results": {"web": {"score": 0.772, "url": "https://www.codejava.net/rest-api/authorization-server-oauth-2-persistent-credentials", "ai_digested_content": "The page shows a Spring Data JPA test that creates OAuth2 clients, encodes client secrets with BCrypt, saves them, and then looks up a client by clientId."}}}} {"query_id": "q6", "query": "java oauth2 code sample", "agent": "gemini-stable", "elapsed_s": 158.234, "ok": true, "response": {"results": {"web": {"score": 0.4, "url": "https://www.codejava.net/rest-api/authorization-server-oauth-2-persistent-credentials", "ai_digested_content": "packagenet.codejava.oauth2;importstaticorg.assertj.core.api.Assertions.assertThat;importjava.util.Optional;importorg.junit.jupiter.api.Test;importorg.springframework.beans.factory.annotation.Autowired;importorg.springframework.boot.test.autoconfigure.jdbc.AutoConfigureTestDatabase;importorg.springframework.boot.test.autoconfigure.jdbc.AutoConfigureTestDatabase.Replace;importorg.springframework.boot.test.autoconfigure.orm.jpa.DataJpaTest;importorg.springframework.security.crypto.bcrypt.BCryptPasswordEncoder;importorg.springframework.security.crypto.password.PasswordEncoder;importorg.springframework.test.annotation.Rollback;@AutoConfigureTestDatabase(replace = Replace.NONE)publicclassClientRepositoryTests {@AutowiredprivateClientRepository repo;publicvoidtestAddClients() {Client client1 = Client.clientId(\"client-1\").name(\"John Doe\").scope(\"read\");Client client2 = Client.clientId(\"client-2\").name(\"Max One\").scope(\"read\");Client client3 = Client.clientId(\"client-3\").name(\"Devi Kumar\").scope(\"write\");Client client4 = Client.clientId(\"client-4\").name(\"Bob Kai\").scope(\"write\");PasswordEncoder encoder =newBCryptPasswordEncoder();client1.setClientSecret(encoder.encode(\"pass1\"));client2.setClientSecret(encoder.encode(\"pass2\"));client3.setClientSecret(encoder.encode(\"pass3\"));client4.setClientSecret(encoder.encode(\"pass4\"));repo.saveAll(List.of(client1, client2, client3, client4));publicvoidtestFindByClientId() {String clientId =\"client-3\";Optional<Client> result = repo.findByClientId(clientId);assertThat(result).isPresent();"}}}} {"query_id": "q6", "query": "java oauth2 code sample", "agent": "devstral-local", "elapsed_s": 17.824, "ok": true, "response": {"results": {"web": {"score": 0.51, "url": "https://www.baeldung.com/java-ee-oauth2-implementation", "ai_digested_content": "```\n@ApplicationPath(\"/api\")\n@DeclareRoles({\"resource.read\", \"resource.write\"})\n@LoginConfig(authMethod = \"MP-JWT\")\npublic class OAuth2ResourceServerApplication extends Application {\n}\n```\n```\n@Path(\"/resource\")\n@RequestScoped\npublic class ProtectedResource {\n@Inject\nprivate JsonWebToken principal;\n@GET\n@RolesAllowed(\"resource.read\")\n@Path(\"/read\")\npublic String read() {\nreturn \"Protected Resource accessed by : \" + principal.getName();\n}\n@POST\n@RolesAllowed(\"resource.write\")\n@Path(\"/write\")\npublic String write() {\nreturn \"Protected Resource accessed by : \" + principal.getName();\n}\n}\n```"}}}} {"query_id": "q6", "query": "java oauth2 code sample", "agent": "gpt-oss-qa", "elapsed_s": 21.364, "ok": false, "error": ""} {"query_id": "q7", "query": "where is the capital city of kazakhstan", "agent": "codex-deputy", "elapsed_s": 9.666, "ok": true, "response": {"results": {"web": {"score": 0.78400004, "url": "https://en.wikipedia.org/wiki/Astana", "ai_digested_content": "Astana, in northern Kazakhstan on the Ishim River."}}}} {"query_id": "q7", "query": "where is the capital city of kazakhstan", "agent": "codex-architect", "elapsed_s": 5.624, "ok": true, "response": {"results": {"web": {"score": 0.98800004, "url": "https://en.wikipedia.org/wiki/Astana", "ai_digested_content": "Astana."}}}} {"query_id": "q7", "query": "where is the capital city of kazakhstan", "agent": "gemini-stable", "elapsed_s": 49.28, "ok": true, "response": {"results": {"web": {"score": 1.0, "url": "https://www.gov.kz/article/19305?lang=en", "ai_digested_content": "Astana"}}}} {"query_id": "q7", "query": "where is the capital city of kazakhstan", "agent": "devstral-local", "elapsed_s": 15.181, "ok": true, "response": {"results": {"web": {"score": 1.0, "url": "https://www.gov.kz/article/19305?lang=en", "ai_digested_content": "Astana"}}}} {"query_id": "q7", "query": "where is the capital city of kazakhstan", "agent": "gpt-oss-qa", "elapsed_s": 11.515, "ok": true, "response": {"results": {"web": {"score": 0.94000006, "url": "https://en.wikipedia.org/wiki/Astana", "ai_digested_content": "Astana is the capital city of Kazakhstan."}}}}