guidance
langchainrb
Our great sponsors
guidance | langchainrb | |
---|---|---|
22 | 16 | |
16,895 | 962 | |
5.3% | - | |
9.8 | 9.5 | |
2 days ago | 1 day ago | |
Jupyter Notebook | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
guidance
-
Show HN: Prompts as (WASM) Programs
> The most obvious usage of this is forcing a model to output valid JSON
Isn't this something that Outlines [0], Guidance [1] and others [2] already solve much more elegantly?
0. https://github.com/outlines-dev/outlines
-
Show HN: Fructose, LLM calls as strongly typed functions
Why do you have Guidance in caps?
https://github.com/guidance-ai/guidance
or ...
https://huggingface.co/docs/text-generation-inference/concep...
or ... ?
A quick glance through these, they don't seem yet to call json_object on OpenAI with the word JSON in the prompt, which works wonders with the 0125 models.
- Forcing AI to Follow a Specific Answer Pattern Using GBNF Grammar
-
Prompting LLMs to constrain output
have been experimenting with guidance and lmql. a bit too early to give any well formed opinions but really do like the idea of constraining llm output.
-
New: LangChain templates – fastest way to build a production-ready LLM app
AutoGen (https://github.com/microsoft/autogen) is orthogonal: it's designed for agents to converse with each other.
The original comparison to LangChain from Microsoft was Guidance (https://github.com/guidance-ai/guidance) which appears to have shifted development a bit. I haven't had much experience with it but from the examples it still seems like needless overhead.
-
Is supervised learning dead for computer vision?
Thanks for your comment.
I did not know about "Betteridge's law of headlines", quite interesting. Thanks for sharing :)
You raise some interesting points.
1) Safety: It is true that LVMs and LLMs have unknown biases and could potentially create unsafe content. However, this is not necessarily unique to them, for example, Google had the same problem with their supervised learning model https://www.theverge.com/2018/1/12/16882408/google-racist-go.... It all depends on the original data. I believe we need systems on top of our models to ensure safety. It is also possible to restrict the output domain of our models (https://github.com/guidance-ai/guidance). Instead of allowing our LVMs to output any words, we could restrict it to only being able to answer "red, green, blue..." when giving the color of a car.
2) Cost: You are right right now LVMs are quite expensive to run. As you said are a great way to go to market faster but they cannot run on low-cost hardware for the moment. However, they could help with training those smaller models. Indeed, with see in the NLP domain that a lot of smaller models are trained on data created with GPT models. You can still distill the knowledge of your LVMs into a custom smaller model that can run on embedded devices. The advantage is that you can use your LVMs to generate data when it is scarce and use it as a fallback when your smaller device is uncertain of the answer.
3) Labelling data: I don't think labeling data is necessarily cheap. First, you have to collect the data, depending on the frequency of your events could take months of monitoring if you want to build a large-scale dataset. Lastly, not all labeling is necessarily cheap. I worked at a semiconductor company and labeled data was scarce as it required expert knowledge and could only be done by experienced employees. Indeed not all labelling can be done externally.
However, both approaches are indeed complementary and I think systems that will work the best will rely on both.
Thanks again for the thought-provoking discussion. I hope this answer some of the concerns you raised
-
Show HN: Elelem – TypeScript LLMs with tracing, retries, and type safety
I've had a bit of trouble getting function calling to work with cases that aren't just extracting some data from the input. The format is correct but it was harder to get the correct data if it wasn't a simple extraction.
Hopefully OpenAI and others will offer something like https://github.com/guidance-ai/guidance at some point to guarantee overall output structure.
Failed validations will retry, but from what I've seen JSONSchema + generated JSON examples are decently reliable in practice for gpt-3.5-turbo and extremely reliable on gpt-4.
-
Show HN: Magentic – Use LLMs as simple Python functions
Right now it just works with OpenAI chat models (gpt-3.5-turbo, gpt-4) but if there's interest I plan to extend it to have several backends. These would probably each be an existing library that implements generating structured output like https://github.com/outlines-dev/outlines or https://github.com/guidance-ai/guidance. If you have ideas how this should be done let me know - on a github issue would be great to make it visible to others.
langchainrb
-
First 15 Open Source Advent projects
8. LangChain RB | Github | tutorial
- Create AI Agents in Ruby: Implementing the ReAct Approach
-
Lost on LangChain: Can someone help with the Question Answer concept?
So I hooked up the Ruby on Rails langchainrb gem (https://github.com/andreibondarev/langchainrb) and it seems like the approach is to store the plane text entries as meta data on pinecone. I definitely DO NOT want to do this as the data is private and secure on my own DB.
-
ruby and ML/AI chatgpt
langchain
This looks promising: LangChain and is similar to it's python counterpart.
-
Emerging Architectures for LLM Applications
Is the emerging architecture made out to be more complicated than what most of the companies are currently building? Perhaps! But this is most likely the general direction where things will start trending towards as the auxiliary ecosystem matures.
Shameless plug: For fellow Ruby-ists we're building an orchestration layer for building LLM applications, inspired by the original, Langchain.rb: https://github.com/andreibondarev/langchainrb
-
Building an app around a LLM, Rails + Python or just Python?
currently in the same boat as you at my company, we've been looking at Boxcars and LangchainRB as our gems but they're pretty new to the scene so not sure about that. I love the idea of langchain for the extensibility of it though - we used the ruby-openai gem for a while but it didn't do what we needed. I'll come back in a week or two with with what we decide (python microservice with flask served api endpoints vs ruby all the way)
I'm the author of Langchain.rb.
-
5 things I wish I knew before building a GPT agent for log analysis
@dliteful23 I loved your super detailed lessons-learned article! I'm the author of Langchain.rb, I would love to hear what you think of it if you get a chance to check it out. If there's anything that you'd like to see in the framework, please do let us know and we'll make sure to build it out if it aligns with the vision.
-
LangChain: The Missing Manual
We’re building “Langchain for Ruby” under the current working name of “Langchain.rb”: https://github.com/andreibondarev/langchainrb
People that have contributed on the project thus far each have at least a decade of experience programming in Ruby. We’re trying our best to build an abstraction layer on top all of the common emerging AI/ML techniques, tools, and providers. We’re also focusbig on building an excellent developer experience that Ruby developers love and have gotten to expect.
Unlike the Python project, as it’s been pointed out here a countless number of times, we’d like to avoid deeply nested class structures that make it incredibly difficult to track and extend.
We’ve been pondering over the “what does Rails for Machine Learning look like?” question, and we’re taking a stab at answering this question.
We’re hyper-focused on the open source community and the developer community at large. All feedback/ideas/contributions/criticism are welcome and encouraged!
What are some alternatives?
lmql - A language for constraint-guided and efficient LLM programming.
semantic-kernel - Integrate cutting-edge LLM technology quickly and easily into your apps
langchain - 🦜🔗 Build context-aware reasoning applications
NeMo-Guardrails - NeMo Guardrails is an open-source toolkit for easily adding programmable guardrails to LLM-based conversational systems.
text-generation-webui - A Gradio web UI for Large Language Models. Supports transformers, GPTQ, AWQ, EXL2, llama.cpp (GGUF), Llama models.
guidance - A guidance language for controlling large language models. [Moved to: https://github.com/guidance-ai/guidance]
ruby-openai - OpenAI API + Ruby! 🤖❤️ Now with Assistants, Threads, Messages, Runs and Text to Speech 🍾
outlines - Structured Text Generation
localLLM_langchain - Local LLM Agent with Langchain
llama-cpp-python - Python bindings for llama.cpp
Microsoft-Activation-Scripts - A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, less antivirus detection and user-friendliness.