HackerTrans
TopNewTrendsCommentsPastAskShowJobs

brockmeier

no profile record

Submissions

[untitled]

1 points·by brockmeier·4 mesi fa·0 comments

[untitled]

1 points·by brockmeier·4 mesi fa·0 comments

[untitled]

1 points·by brockmeier·4 mesi fa·0 comments

[untitled]

1 points·by brockmeier·4 mesi fa·0 comments

[untitled]

1 points·by brockmeier·4 mesi fa·0 comments

[untitled]

1 points·by brockmeier·5 mesi fa·0 comments

Show HN: Notion Breadcrumb Navigator – Keyboard-driven page hierarchy navigation

github.com
2 points·by brockmeier·5 mesi fa·0 comments

Show HN: VoxPaste – Fast voice-to-text CLI for dictating to Claude/Cursor

github.com
2 points·by brockmeier·5 mesi fa·2 comments

Data manipulation using natural language prompts

4 points·by brockmeier·anno scorso·5 comments

Show HN: Grammarly for Prompts Built with Go, Htmx, Templ

lemonai.onrender.com
3 points·by brockmeier·3 anni fa·0 comments

Show HN: Lemon Agent – Plan and Solve agent for workflow automation

github.com
7 points·by brockmeier·3 anni fa·2 comments

Show HN: Lemon AI – open-source Zapier NLA to empower agents

github.com
13 points·by brockmeier·3 anni fa·7 comments

comments

brockmeier
·5 mesi fa·discuss
Also, the new Mistral model is unbelievably fast:

https://simonwillison.net/2026/Feb/4/voxtral-2/

And the costs of usage are very low. For instance, with voxtral-mini-latest, you you can dictate for 5.5 hours and only have to pay $1:

https://mistral.ai/pricing#api
brockmeier
·5 mesi fa·discuss
Just added openrouter support as well.
brockmeier
·3 anni fa·discuss
This is really cool! I’m doing something similar with Lemon Agent (https://github.com/felixbrock/lemon-agent). What I find most powerful about defining workflows in a json file is that you can add additional fields to let the LLM know about specific execution requirements, like asking the user for permission before executing a specific workflow step. This allows for infinite configuration options. Curious to hear if you already experimented with something like this or if you are planning to include something similar?
brockmeier
·3 anni fa·discuss
I think Zapier's NLA solution goes in a similar direction and as far as I know, they are running their model on the server side to adjust workflow input and output of workflows to the unique needs of an LLM model. They are doing an amazing job there and I am also currently working on improving this (e.g. adjusting to a model's token limit).

Besides that, Lemon Agent focuses on providing an out-of-the-box agent that is great at solving tasks with workflow automation. If you want to use Zapier NLA you have to rely on generalistic agents like LangChain's ReAct Agent or the Plan and Execution Agent or you have to build your own agent. In any case, you have to twist the agent a lot to reach a certain degree of accuracy and reliability.
brockmeier
·3 anni fa·discuss
Thanks a lot for sharing this, we really like gorilla! This is definitely on our roadmap.
brockmeier
·3 anni fa·discuss
I think it’s best to view this separately. Langchain provides its own agent type (next to the commonly used ReAct agent) to interact with OpenAI functions. Lemon AI functions are standalone fallback mechanisms that will be used by the model in specific situations where near-deterministic model behavior is especially important, a bit similar to the functions offered by OpenAI just suitable for open source models. You can combine Lemon functions with any Langchain agent type. Hope this helps!
brockmeier
·3 anni fa·discuss
Foundry is doing a nice job bringing functions in LLM apps to life. That's something I am also working on with Lemon AI functions. Besides that, to me it seems that it’s focused on read operations for web-based services. What I’m building is focused on allowing for read and write operations, both for internal tooling and web services to allow agents to take actions based on instructions. I’m essentially focussing on helping Langchain users to establish end-to-end workflow automation as quickly as possible. Going forward permission workflows will be covered as well so assistants can be team / user specific, something that I believe isn’t solved well by Zapier NLA right now.