Live data from Hacker News

Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI

github.com

1–10 of 38 posts

Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI

#1
Hello HN! The day has finally come to stop adding features and start sharing what I've been building the last 5-6 months.

It's a bit of CrewAI, OpenDevon, LangFuse/Cloud all in one, providing devs who prefer TypeScript an integrated framework thats provides a lot out of the box to start experimenting and building agents with.

It started after peeking at the LangChain docs a few times and never liking the example code. I began experimenting with automating a simple Jira request from the engineering team to add an index to one of our Google Spanner databases (for context I'm the DevOps/SRE lead for an AdTech company).

It incudes the tooling we're building out to automate processes from a DevOps/SRE perspective, which initially includes a configurable GitLab merge request AI reviewer.

The initial layer above Aider (https://aider.chat/) grew into coding agent and an autonomous agent with LLM-independent function calling with auto-generated function schemas.

And as testing via the CLI became unwieldy soon grew database persistence, tracing, a Web UI and human-in-the-loop functionality.

One of the more interesting additions is the new autonomous agent which generates Python code that can call the available functions. Using the pyodide library the tool objects are proxied into the Python scope and executed in a WebAssembly sandbox.

As its able to perform multiple calls and validation logic in a single control loop, it can reduce the cost and latency, getting the most out of the frontier LLMs calls with better reasoning.

Benchmark runners for the autonomous agent and coding benchmarks are in the works to get some numbers on the capabilities so far. I'm looking forward to getting back to implementing all the ideas around improving the code and autonomous agents from a metacognitive perspective after spending time on docs, refactorings and tidying up recently.

Check it out at https://github.com/trafficguard/nous

Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI
github.com

Re: Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI

#3

That trace UI is nice

I can't take credit for that particular screen, it's the Trace UI in Google Cloud. I did look at LangSmith for tracing, but for now I wanted to stick with standard OpenTelemetry tracing, so you could export the spans to Honeycomb etc

Re: Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI

#6
post #4

If this isn't by Nous Research, may want to consider renaming ( https://x.com/NousResearch , https://nousresearch.com/ )

And if it is is by Nous Research we there definitely needs to be clearer branding as this is very confusing.

If OP is not Nous Research (which I suspect to be the case) then a name change is a must as they're already a fairly well established company in the LLM space (surprised OP isn't aware of the name collision already). It's a bit similar to creating a new library with the "Smiling Face with Open Hands emoji"[0] as your logo

0. https://emojipedia.org/hugging-face

Re: Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI

#7
post #4

If this isn't by Nous Research, may want to consider renaming ( https://x.com/NousResearch , https://nousresearch.com/ )

And if it is is by Nous Research we there definitely needs to be clearer branding as this is very confusing. If OP is not Nous Research (which I suspect to be the case) then a name change is a must as they're already a fairly well established company in the LLM space (surprised OP isn't aware of the name collision already). It's a bit similar to creating a new library with the "Smiling Face with Open Hands emoji"[0]…

Never heard of you

Re: Show HN: Nous – Open-Source Agent Framework with Autonomous, SWE Agents, WebUI

#9
post #4

If this isn't by Nous Research, may want to consider renaming ( https://x.com/NousResearch , https://nousresearch.com/ )

And if it is is by Nous Research we there definitely needs to be clearer branding as this is very confusing. If OP is not Nous Research (which I suspect to be the case) then a name change is a must as they're already a fairly well established company in the LLM space (surprised OP isn't aware of the name collision already). It's a bit similar to creating a new library with the "Smiling Face with Open Hands emoji"[0]…

When I first picked the name, after a chat with Claude, I hadn't come across Nous Research back then, and they didn't show up Googling for just nous.

I see a bit of reuse of words in other various llm related projects.

Langchain/langfuse/langflow

Llama/ollama/llamaindex

so I hadn't been too worried about it when became aware of them.

That's what Show HN is for, getting feedback, and a name changed now would be easy before I post it around more.

Post reply on HN