Skip to content

[Question] CodeAct Architectures #1526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
austinmw opened this issue Apr 6, 2025 · 2 comments
Open

[Question] CodeAct Architectures #1526

austinmw opened this issue Apr 6, 2025 · 2 comments

Comments

@austinmw
Copy link

austinmw commented Apr 6, 2025

Hi, I'm curious how you see CodeAct architectures fitting into MCP? CodeAct has seen some recent buzz with the introduction of Manus and other chat agents which use it and demonstrating improved tool calling speed and accuracy.

Right now LLMs are using tools as black boxes through API supported tool-use via writing JSON tool calls.

If CodeAct becomes more performant and we transition to importing code modules as tools and executing them in sandboxes, a standard will still be required for defining these modules in the best way for LLMs, and we'll also need a way to serve access to these code module tools.

Curious if there are any thoughts that can be shared around this?

@sohamganatra
Copy link
Contributor

Hey @austinmw, So we are very bullish on "Code Generation for Function Calling" as we have observed some very good early results testing it. I believe there are MCP compatible ways to do it and I am planning to create a small prototype soon to test it out.

I agree a new standard might emerge for CodeAct but MCP can also be made compatible with few tweaks.

@austinmw
Copy link
Author

austinmw commented Apr 8, 2025

Appreciate your response, would love to see a prototype when you're ready to share!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants