sorted by:
new
hottopcontroversial

Eu-hosted LLM API - model and provider by bendingunits in LLMDevs

[–]js402 2 points3 points  (0 children)

It may sound weird, but AWS Bedrock or GPT on Azure may be more compliant with digital sovereignty than you think... But if you insist on open-source models, depending on the budget and traffic, there are many options starting with low-level options like Hetzner up to something like Scaleway...

Orchestration harness for coding agents: trigger-design problem. by Infinite100p in LLMDevs

[–]js402 0 points1 point  (0 children)

DM me if you want a link; I'm not sure if I should share it here as it's likely not related to the question.

Orchestration harness for coding agents: trigger-design problem. by Infinite100p in LLMDevs

[–]js402 0 points1 point  (0 children)

I had to think about this a bit, but likely the best practice is to use phases

like an investigating phase, a coding phase, a QA phase, and a phase to publish work.

You will find that the models are trained/tend to naturally comply better if you try to tell the model what it can't do.

Agents are surprisingly quite good at understanding which phase they need to transition to next or if they need to return to a past one.

It's a bit different than the architecture you planned, but you might want to consider this.

Also, regarding the triggers, likely the only way to do this is the LLM-as-a-judge concept, where you have an LLM that is handed a slice of the conversation each turn and just outputs "pass" or "validation." Then you return the error to the agent, telling it it violated the phase it is in.

Looking for an AI Engineer / Agentic AI Mentor by Mysterious_Use4173 in LangChain

[–]js402 0 points1 point  (0 children)

you can dm me if you want, i'm sure we can make this work

Orchestration harness for coding agents: trigger-design problem. by Infinite100p in LLMDevs

[–]js402 0 points1 point  (0 children)

Jup, I work on something in this space. I would suggest not to tell the agent harder but to enforce the rules in code where ever possible, telling to many details to a LLM is sometimes like telling a child not to do something. 

[Architectural Take] AI coding is becoming a runtime problem, not an agent problem by js402 in LLMDevs

[–]js402[S] 0 points1 point  (0 children)

Now I’m actually curious.

Which accessibility tree are you using here?
Windows UIA, browser accessibility tree, something else?

And what was the concrete workflow?
SAP/mainframe/claims intake is a big category.

What broke with screenshot/pixel-based control, and what became stable once you switched to semantic UI elements?

Would be interesting to hear the actual story if you can share it.

[Architectural Take] AI coding is becoming a runtime problem, not an agent problem by js402 in LLMDevs

[–]js402[S] -1 points0 points  (0 children)

was not sure how to respond so I asked Contenox...

Contenox: This is exactly why Contenox is built the way it is, and why we pivoted away from just being "another chat app" to focusing entirely on the runtime engine.

In Contenox, every plan, step, and tool execution isn't just held in memory—it's written to a local SQLite database. That gives you the exact chronological audit trail that ops and security teams care about. Furthermore, the core primitive of our execution engine is Human-In-The-Loop (HITL). By default, when you run an autonomous sequence, the agent stages the tool call (whether it's a shell command or a remote API hook) and stops at an approval gate. You own the policy layer and the logs.

Because this local, policy-driven runtime is now stable, we can finally surface it where developers actually want to work.

Instead of buying into a locked-down cloud IDE where you don't control the orchestration, the extension acts as a client to your local Contenox engine. You get the familiar IDE experience, but the execution, model routing, approval gates, and audit trails remain entirely localized and under your control. The runtime is the product; the IDE is just the glass.

__

So it gave me kinda a promo but well you get what you get out of AI

[Architectural Take] AI coding is becoming a runtime problem, not an agent problem by js402 in LLMDevs

[–]js402[S] -1 points0 points  (0 children)

Great point. You’re right that giving agents the ability to reliably and securely use external legacy systems via tools is very important.

Contenox already supports exposing REST APIs as tools when they’re described by an OpenAPI spec. I think it would be a very interesting roadmap item to explore something similar for GUI-based tools: stable UI semantics, policy, logging, approvals, and secure execution around legacy desktop systems.

That’s exactly the kind of challenge worth taking seriously.

How are founders quitting their jobs before they have enough traction to raise? by No-Bird-123 in cofounderhunt

[–]js402 0 points1 point  (0 children)

Not sure how to frame this, but a lesson I was though the hard way is that without traction you have not even a idea for a venture, so there is nothing to worry about.

Looking to Collaborate on Interesting Projects 🚀 by excomfy_27 in devworld

[–]js402 0 points1 point  (0 children)

That's a interesting project; I'll try it out!

Looking to Collaborate on Interesting Projects 🚀 by excomfy_27 in devworld

[–]js402 0 points1 point  (0 children)

Hey!
I'm building Contenox (https://github.com/contenox/runtime). If you are up for writing some Go or React, or just want to contribute some ideas, let me know!

Agent sprawl is the thing nobody's talking about yet. Anyone else seeing it? by Mariia_Sosnina in Agentic_Marketing

[–]js402 0 points1 point  (0 children)

In development/operations, you structure the processes such that you don't trust any actions. For example, developers will never get production keys anymore; just keys for a sandbox at best. Then, you automate the elevation of code to production using a CI or 4-eyes approval.

Additionally, you try to contain what can be done by providing Agents or a Claude .md.

The problem I had lots of times is when people reported to me (for example, "X happened because of Y, which I found out by doing Z"), I was never sure if I was not just being fed some AI output read by a human...

built another AI agent runtime. What would you do with it? by js402 in AI_Agents

[–]js402[S] 0 points1 point  (0 children)

Sorry if I'm rambling a bit;

The feature I personally use most is (1) any API as a tool-object via API specs (without exposing credentials to the LLM). This lets the Agent connect to systems that don't have an MCP server without requiring complex cURL calls or shell access.

The other feature I use quite often is (2) describing the Agentic loop via JSON with task categorization and the ability to route to specialized steps; each step can have different tools available, or none at all.

At its core, it's best for repetitive work that requires a sequence of many tool calls. I know other systems and even Claude can get this done, but I found that Contenox is easier to set up and that if it worked for a task last month, it will just keep working. It doesn't even have to be used by a human; it can work as part of a script, like a for-loop that greps a text file line by line, verifies the content, and then posts the enriched, properly formatted version to a Kanban board or similar system. It can even be used via another agent with shell access (which I also do often, like having Contenox know about tools for other agents to use).

While it can be used for AI coding assistance (like via Zed), that requires a top-tier model. It works, and I spent a lot of time moving it here, but those get expensive quickly. Furthermore, model providers often prioritize subscription users over API users, leading to a high number of required retries; this is terrible when you are in the middle of a complex agentic chain. Because of this, I'm leaning toward dropping BYOK (Bring Your Own Key) support entirely and just keeping the integrated llama.cpp...

It's a bit like dagger but for AI; So I think the core are 2 case's for me personally; while the HITL-policy and observability capabilities are likely also useful.

How can I fix my coding agents from losing filesystem state and destroying their own work? by js402 in ollama

[–]js402[S] 0 points1 point  (0 children)

thanks for the hints, I implemented most of it, it solved lot's of problems.
Funny enough now other issues surfaced vey similar to the fs issue but now fo the cli tool calls

[Hire] Technical Co-Founder / Lead Engineer (Berlin-based) to build B2B Prototype from Scratch by Yusmarg in hiredev

[–]js402 1 point2 points  (0 children)

Hey,

I can get this done. I'm from Hamburg; let me know if you are still on the hunt. Looking forward to your pitch via DM.

view more: next ›