awesome-ai-agents VS Voyager

# TODO: Get your Groq AI API key from https://console.groq.com/ GROQ_API_KEY = "" # TODO: Get your E2B API key from https://e2b.dev/docs E2B_API_KEY = "" # Or use 8b version # MODEL_NAME = "llama3-8b-8192" MODEL_NAME = "llama3-70b-8192" SYSTEM_PROMPT = """you are a python data scientist. you are given tasks to complete and you run python code to solve them. - the python code runs in jupyter notebook. - every time you call `execute_python` tool, the python code is executed in a separate cell. it's okay to multiple calls to `execute_python`. - display visualizations using matplotlib or any other visualization library directly in the notebook. don't worry about saving the visualizations to a file. - you have access to the internet and can make api requests. - you also have access to the filesystem and can read/write files. - you can install any pip package (if it exists) if you need to but the usual packages for data analysis are already preinstalled. - you can run any python code you want, everything is running in a secure sandbox environment""" tools = [ { "type": "function", "function": { "name": "execute_python", "description": "Execute python code in a Jupyter notebook cell and returns any result, stdout, stderr, display_data, and error.", "parameters": { "type": "object", "properties": { "code": { "type": "string", "description": "The python code to execute in a single cell.", } }, "required": ["code"], }, }, } ]

Hey everyone! I'm the CEO of the company that built this SDK.

We're a company called E2B [0]. We're building and open-source [1] secure environments for running untrusted AI-generated code and AI agents. We call these environments sandboxes and they are built on top of micro VM called Firecracker [2].

You can think of us as giving small cloud computers to LLMs.

We recently created a dedicated SDK for building custom code interpreters in Python or JS/TS. We saw this need after a lot of our users have been adding code execution capabilities to their AI apps with our core SDK [3]. These use cases were often centered around AI data analysis so code interpreter-like behavior made sense

The way our code interpret SDK works is by spawning an E2B sandbox with Jupyter Server. We then communicate with this Jupyter server through Jupyter Kernel messaging protocol [4].

We don't do any wrapping around LLM, any prompting, or any agent-like framework. We leave all of that on users. We're really just a boring code execution layer that sats at the bottom that we're building specifically for the future software that will be building another software. We work with any LLM. Here's how we added code interpreter to the new Llama-3 models [5].

Our long-term plan is to build an automated AWS for AI apps and agents.

Happy to answer any questions and hear feedback!

[0] https://e2b.dev/

[1] https://github.com/e2b-dev

[2] https://github.com/firecracker-microvm/firecracker

[3] https://e2b.dev/docs

[4] https://jupyter-client.readthedocs.io/en/latest/messaging.ht...

[5] https://github.com/e2b-dev/e2b-cookbook/blob/main/examples/l...

github.com/awesome-ai-agents

Github: https://github.com/e2b-dev/awesome-ai-agents and https://github.com/EmbraceAGI/Awesome-AGI

Source: Conversation with Bing, 12/10/2023 (1) Wes Roth - YouTube. https://www.youtube.com/@WesRoth. (2) I've set most of my videos to Public again - Community. https://community.openai.com/t/ive-set-most-of-my-videos-to-public-again/24535. (3) AI Updates: Meta Develops Mind-Reading AI System, OpenAI’s Q* Is Here .... https://www.windermeresun.com/2023/11/20/ai-updates-meta-develops-mind-reading-ai-system-openais-q-is-here-how-economy-will-work-after-agi/. (4) David Shapiro. https://www.daveshap.io/. (5) undefined. https://natural20.com/. (6) undefined. https://arxiv.org/abs/2305.16291. (7) undefined. https://twitter.com/DrJimFan/status/1. (8) undefined. https://voyager.minedojo.org/. (9) undefined. https://minedojo.org/. (10) undefined. https://www.youtube.com/@DavidShapiroAutomator/videos.

> AI cannot sustain itself trained on AI work.

This isn’t true. You can train LLMs entirely on synthetic data and get strong results. [0]

> If new languages, engines etc pop up it cannot synthesize new forms of coding without that code having existed in the first place.

You can describe the semantics to a LLM, have it generate code, tell it what went wrong (i.e. with compiler feedback), and then train on that. For an example of this workflow in a different context, see [1].

> And most importantly, it cannot fundamentally rationalize about what code does or how it functions.

Most competent LLMs can trivially describe what some code does and speculate on the reasoning behind it.

I don’t disagree that they’re flawed and imperfect, but I also do not think this is an unassailable state of affairs. They’re only going to get better from here.

[0]: https://arxiv.org/abs/2309.05463

[1]: https://voyager.minedojo.org/

In a way it is the same thing, agents are mostly an abstraction that make it easier to know what’s going on.

I think of agents more or less as python classes with a mixture of natural language and code functions. You design them to do something with information they produce, and to interface with other agents or “tools” in some way.

But all the agents can be the same language model under the hood, they are frames used to build different kinds of contexts.

And yes I think the idea is that emergent behaviour can be useful. This comes to mind

https://github.com/MineDojo/Voyager

But I think we are still a small ways off from being really smart about agents. My opinion is that we haven’t quite figured out what we are doing yet.

This k8s application deploys an instance of Voyager along with a Fabric Minecraft server with required fabric mods. It assumes you have a local deployment of a Large Language Model (LLM) with 4K-8K token context length with a compatible OpenAI API, including embeddings support.

In my opinion the most interesting Agents: Auto-GPT Github: https://github.com/Significant-Gravitas/Auto-GPT BabyAGI Github: https://github.com/yoheinakajima/babyagi Voyager Github: https://github.com/MineDojo/Voyager / Paper: https://arxiv.org/abs/2305.16291 I would also add: ChemCrow: Augmenting large-language models with chemistry tools Github: https://github.com/ur-whitelab/chemcrow-public/ Paper: https://arxiv.org/abs/2304.05376

Does this beat the voyager? I read about it and wondered what if we add a skill library to langchain/llamaindex agents. It could be the same vector store for storing static data but after each task is performed, the agent will evaluate and archive the recipe of steps to perform a new task. Next time when the agent is asked to perform a task, it can just look at the library to retrieve a recipe. Unlike traditional fine tuning, you dont update the model parameters, these recipes are much more interpretable and can be manually edited/inserted by humans. There may also be an automatic way to convert wikihow articles or youtube tutorials into recipes.

Source. P.S. If you love geeking over AI updates, I have this free newsletter you might want to check out. Thank you!

Source.