Viewing profile — zambelli

v0.7.1 is now out - Forge can now sit behind Claude Code! Proxy mode can talk to supported backends and handles format translation. Anthropic > forge > OpenAI; or Anthropic > forge…

Thanks for the thoughtful comment! Let me try to unpack some of what's there and what's missing. Forge is at its core a mechanical reliability layer, whereas a lot of memory/skill …

You're very welcome! I've seen some good PRs come through and merges are starting. I need 24-48 hours to get the conference demo and travel sorted then work can continue at a faste…

Thanks to everyone for the great discussion! v0.7.0 is out now. It was in flight when this landed - changes tool error channel based on dogfooding observations with some larger mod…

This is a really neat writeup, and the empirical data for coding agents is super useful. Will take a closer read and see if there's anything I easily lift into my harness!

Merged! Thanks for that catch. I'll try to sequence the in-flight work ASAP to get the vllm branch merged in as a whole.

Oh that's a good find, I'll book ark this for a GitHub issue. Glad to hear it's working!

Yeah I got it working as a quick test run to confirm a model issue vs backend issue on a consumer app. It worked on my dual-5070 Ti rig, but I didn't have time to formalize all the…

[dead]

Nice symmetry with tool call failures being sent to LLM that made the call without bugging the user. The artifact-generating entity gets the error back, effectively. 100% correct, …

Oh, interesting - thanks for the link. I really haven't explored this but it should slot in fairly easily I think? Gotta dig into it more.

Very cool! I'll try to get an issue open on lmstudio support and add it to the backlog.

Interesting, catching the problem upstream, effectively. How did you enforce the grammar?

Retry nudges do generate an extra LLM call, and those average extra calls time impacts are captured in the eval data. But that's the difference between the call failing and succeed…

Oh, awesome! I'll take a look.

[dead]

Thank you! I've been trying to catch those replies and redirect people, but hopefully your comment be upvoted for others. Very embarrassing to put up the post with the wrong link l…

Ohhhh, that's much more interesting. I haven't looked into that at all, but now I'm curious. I'd need to think way more about how to layer that into forge, but the principle could …

This is not an agentic coding harness. It's a generic tool-calling guardrail stack. I have built a coding harness built on Forge since, but that's not what this is.

Nice ;). I'll take a closer read of it, that's on me - I am definitely seeing more people looking in this direction as agents start to ramp in production at the enterprise level, w…

I know :( - I posted the wrong link and now it's there forever. Dashboard is in here: https://github.com/antoinezambelli/forge/tree/main/docs/resu...

Not stupid at all! Some of the older models did do this (like 3.5-era ish I think), and the harness would parse the results. The newer way frontier has setup is structured tool cal…

Yeah I would think so! A lot of current tooling is layered mostly at the workflow level. Auth for the agent, or memory management for the agent (like some smart skills stuff), but …

Thanks! No this was my own time, just evenings and weekends - life-permitting.

Love this question! A few points: - First, there's totally a "risk" there. I built both the harnesses and the eval suite and that's hardly a double-blind study. There's no world wh…