arthurjean

4 ms·

1.
Show HN: Rust Doctor, a code health scanner for Cargo workspaces(github.com)
2 points by arthurjean 2mo ago|0 comments
2.
Show HN: Paneflow – cross-platform GPUI app for parallel coding agents(github.com)
2 points by arthurjean 3mo ago|0 comments
3.
by arthurjean 6mo ago
Same here. It's not airtight, the agent could technically read the wrapper or env vars, but in practice it doesn't bother. Good enough for most setups.
4.
by arthurjean 6mo ago
You're right actually. Exa's MCP server is stateless, just a REST wrapper. A skill + CLI would do the same job with way less context cost. Someone already built that ( https://github.com/tobalsan/exa ).
5.
by arthurjean 6mo ago
Most of the time you should. But it depends on what you're wrapping. Exa is a good example of where MCP makes sense, it's not just one API call, it's 4 different tools (web search, code search, crawling, advanced search) plus
6.
by arthurjean 6mo ago
It even ships a bundled rg binary via @vscode/ripgrep — you can switch to your system rg with USE_BUILTIN_RIPGREP=0 for better perf. One gotcha worth knowing: in non-git repos, .gitignore rules are silently ignored because rg doesn&#x2
7.
by arthurjean 6mo ago
MCP earns its keep in specific cases: when the agent has no shell access, when you need to keep credentials out of the prompt context, or when you want runtime tool discovery across teams. But I've built a few MCP servers and half of t
8.
by arthurjean 7mo ago
I've used both. I stuck with Claude Code, the ergonomics are better and the internals are clearly optimized for Opus which I use daily, you can feel it. That said OpenCode is still a very good alternative, well above Codex, Gemini CLI
9.
by arthurjean 7mo ago
Sounds about right for someone who ships fast and iterates. 54 days for a v0 that probably needs refactoring isn't that crazy if the dev has a real DB background. We've all seen open source projects drag on for 3 years without shi