Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shad42
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
1.
▲
Mendral Team Joins Anthropic
(mendral.com)
2 points
by
shad42
2mo ago
|
1 comments
2.
▲
Automating the engineering work that isn't your product
(mendral.com)
2 points
by
shad42
3mo ago
|
0 comments
3.
▲
How we know if our agent is right
(mendral.com)
3 points
by
shad42
4mo ago
|
0 comments
4.
▲
by
shad42
4mo ago
Dependabot is focused on upgrading dependencies, and nothing else. One of your dep is outdated, here is an update. Mendral is smarter when updating deps, it looks at newer version, scans for vulnerabilities or upgrade patterns that can put
5.
▲
Not update your dependencies in 2026
(mendral.com)
1 points
by
shad42
4mo ago
|
0 comments
6.
▲
Supply chain attacks don't wait for CVEs
(mendral.com)
3 points
by
shad42
4mo ago
|
0 comments
7.
▲
We built an agent for CI despite using Claude Code for everything else
(mendral.com)
2 points
by
shad42
4mo ago
|
0 comments
8.
▲
We built an agent specialized for CI (using the 3 Claude models)
(mendral.com)
2 points
by
shad42
4mo ago
|
0 comments
9.
▲
How we know if our agent is right
(mendral.com)
2 points
by
shad42
4mo ago
|
0 comments
10.
▲
How we know if our agent is right
(mendral.com)
5 points
by
shad42
5mo ago
|
0 comments
11.
▲
by
shad42
5mo ago
In this post, we built the harness, it’s not 3rd party (like Claude code in a sandbox). So we trust it as much as the rest of our backend code.
12.
▲
by
shad42
5mo ago
No, for example a tool call calling an API. So the llm does not have access to the API keys, the tool does. For example an API call that fetches some data remotely and return it to the llm. You don’t need a sandbox for it. It’s faster and m
13.
▲
by
shad42
5mo ago
We don't host 3rd party agents (I don't know if this what you implied). We built an agent that monitors CI pipelines, tests failures, performance and auto opens PR to address issues we find. We host our agent loop on a backend (it
14.
▲
by
shad42
5mo ago
Yes, it's also because the agent described in the post is doing some operations on the user code (fix CI pipelines, rerun tests, fix them, etc...). So another big reason to use the sandbox is to run things like bash on a user code. you
15.
▲
The agent harness belongs outside the sandbox
(mendral.com)
182 points
by
shad42
5mo ago
|
121 comments
16.
▲
by
shad42
5mo ago
We considered wrapping Claude Code when we started building Mendral (this agent in the article). We ended up building our own agent, it's lot more work because we followed all the right patterns as the models evolved (sub-agents, prope
17.
▲
by
shad42
5mo ago
Nice, it's on our todo list to use oss models too. What are you building?
18.
▲
by
shad42
5mo ago
Curious, what steps did you follow to end up with this design (what did you try before)? And what's your use case for this agent?
19.
▲
by
shad42
5mo ago
IMO RAG is mostly dead. The game changer with newer models like Opus is the reasoning. So instead of pushing all the context up front (RAG style), it's better to give strong primitives (eg. bash, SQL) and let the agent figure it out. I
20.
▲
by
shad42
5mo ago
We're dealing with CI logs, produced by a variety of frameworks, languages, etc... And the tough ones to look into are e2e tests, with outputs from infrastructure. I wish a re.match() would be enough, but we often don't even know
21.
▲
by
shad42
5mo ago
It's the same as an escalation. Something we omitted from the post is that we often use Sonnet to write SQL queries. We wrote another post that was on HN some time ago that goes into the details of SQL queries (linked at the top of thi
22.
▲
by
shad42
5mo ago
I am one of Mendral co-founder (my co-founder wrote the article), I am the one to blame for changing the title when posting. I thought our original one was too clickbait and I wanted to better summarize with this title. Despite the original
23.
▲
We decreased our LLM costs with Opus
(mendral.com)
106 points
by
shad42
5mo ago
|
31 comments
24.
▲
Multi-player agents don't fit in the sandbox
(mendral.com)
2 points
by
shad42
5mo ago
|
0 comments
25.
▲
We built our AI agent, for analyzing CI logs
(mendral.com)
1 points
by
shad42
5mo ago
|
0 comments
26.
▲
Same LLM, different agent: a CI debugger built on Claude
(mendral.com)
2 points
by
shad42
5mo ago
|
0 comments
27.
▲
Agent Harness: Inside vs. Outside the Sandbox
(mendral.com)
3 points
by
shad42
5mo ago
|
0 comments
28.
▲
Same LLM but different output: we built a CI specialist
(mendral.com)
1 points
by
shad42
5mo ago
|
0 comments
29.
▲
We upgraded our agent to Opus and our costs went down
(mendral.com)
2 points
by
shad42
5mo ago
|
0 comments
30.
▲
Same LLM, Different Agent: What Changes When You Specialize for CI
(mendral.com)
3 points
by
shad42
6mo ago
|
0 comments
More ›