-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Add A Stateful Dev Environment by Jupiter example to gallery #1376
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1376 +/- ##
=======================================
Coverage 32.48% 32.48%
=======================================
Files 41 41
Lines 4907 4907
Branches 1120 1120
=======================================
Hits 1594 1594
Misses 3187 3187
Partials 126 126
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It’s weird PR description but okay…
Should wait for the author of notebook first.
I made some edits to the description. @olimoz waiting for your final resolution :D |
77daccb
to
b190bc8
Compare
Woops, bit late to this conversation. Please go ahead. Meanwhile, I have drafted an implementation of the code executor for Jupyter Notebooks. Uses capability, add_to_agent() and a NotebookCodeExecutor which is inspired by IPythonCodeExecutor at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo in description, spurious 's' after 'Team'.
Should read....
"description": "An AutoGen Team Powered by Jupyter Notebook."
…ft#1376) Co-authored-by: Chi Wang <[email protected]>
…ft#1376) Co-authored-by: Chi Wang <[email protected]>
Why are these changes needed?
Jupyter Notebooks offer agents:
stateful code execution
a record of the conversation
an iterative environment where the team can ReAct to data and errors as the project progresses.
Notebooks also allow us humans to examine the team's output in a convenient format and even return to the notebook at a later date, to pick up from where we left off.
Most importantly, this implementation is easy and requires little code
Checks