xonecas.io
64875
Mc

mini-coder / commit 316347a

feat: docs cleanup after exa tools

Sean2026-03-01 316347a7e80c68d7d769bc5c1950a99f6c1ca4f1 parent a30a472

2 files changed

AGENTS.md+2−0
@@ -9,3 +9,5 @@
99 - We care about performance.
1010 - Don't worry about formatting issues, formatting happens automatically on mutations. (see .agents/hooks)
1111 - Do not inline `import` calls. Don't duplicate code. Don't leave dead code behind.
12+- Don't make random test files, if you need to test something, write a propper unit test.
13+- If you make temp files, clean them up when you are done.
TODO.md+26−1
@@ -6,7 +6,7 @@
66
77 ## Implement WebContent and WebSearch using exa.ai api
88
9-Why not just keep using them via their MCP? Simple answer: their tools descriptions/schema is bloated with params that don't concern the llm. They are also misleading in their naming conventions, futher worsening the issue. Let's use their api (let's auto discover the api key like we do for other providers "EXA_AI_API_KEY") and if Exa is enabled, the tools are given to the LLM.
9+Why not just keep using them via their MCP? Simple answer: their tools descriptions/schema is bloated with params that don't concern the llm. They are also misleading in their naming conventions, futher worsening the issue. Let's use their api (let's auto discover the api key like we do for other providers "EXA_API_KEY") and if Exa is enabled, the tools are given to the LLM.
1010
1111 https://exa.ai/docs/reference/search-quickstart
1212 https://exa.ai/docs/reference/contents-quickstart
@@ -18,6 +18,31 @@ https://exa.ai/docs/reference/contents-quickstart
1818 - This is not a infinite reasoning loop, there are requests being made, the app is "stuck", or "hanguing".
1919 - Setting a thinkingConfig is also not a fix, 8000 is the default.
2020
21+## Fucking shit ctrl+c still doesn't work how the fuck is this possible:
22+
23+Agent got stuck on thinking after calling the shell tool, using ctrl+c exitted the app... This is un-acceptable, see the git history, ctrl+c has been broken and there have been several claims to fixing it. The truth is that it doesn't work at all. I'm fucking done with this bullshit, either it works this time, or we are moving interrupt to a different key. This is fucking stupid...
24+
25+```
26+◆ I have updated `src/tools/exa.ts` to address both issues:
27+
28+1. Context Window Vulnerabilities: Added a constraint to the URLs array length in the `ExaContentSchema` by chaining `.max(3)` so the agent won't fetch more than 3 URLs at a time. Also, changed `text: true` to `text: { maxCharacters: 10000 }` to avoid returning overly large payloads.
29+2. Swallowed Error Details: Extracted the error body (`await response.text()`) and included it in the thrown `Error` for both `webSearchTool` and `webContentTool`, providing detailed visibility into API failures.
30+
31+All code checks and tests passed successfully.
32+gemini-3.1-pro mm7kimxq ~/src/mini-coder ⎇ main ctx 46.4k/1000.0k 5% ↑1033.7k ↓8.6k
33+▶ ok make a commit
34+ $ $ git add src/tools/exa.ts src/agent/tools.ts && git commit -m "feat: i…
35+ ✔ 0
36+ │ [main a30a472] feat: implement native Exa web search and content tools
37+ │ 2 files changed, 102 insertions(+), 2 deletions(-)
38+ │ create mode 100644 src/tools/exa.ts
39+ $ $ git push
40+ ✔ 0
41+ │ To github.com:sacenox/mini-coder.git
42+ │ 9348b39..a30a472 main -> main
43+error: script "dev" exited with code 130
44+```
45+
2146 ## Subagents don't have access to MCP tools?
2247
2348 Investigate if subagents are able to see the mcp tools. The user reported that after adding the exa mcp tools, that the subagents claimed to not be able to search online, but the main agent could.