You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+16
Original file line number
Diff line number
Diff line change
@@ -118,3 +118,19 @@ Args:
118
118
agent_type (str): Agent type to handle this subscription
119
119
"""
120
120
```
121
+
122
+
## Docs when adding a new API
123
+
124
+
Now that 0.4.0 is out, we should ensure the docs between versions are easy to navigate. To this end, added or changed APIs should have the following added to their docstrings respectively:
125
+
126
+
```rst
127
+
.. versionadded:: v0.4.1
128
+
129
+
Here's a version added message.
130
+
131
+
.. versionchanged:: v0.4.1
132
+
133
+
Here's a version changed message.
134
+
```
135
+
136
+
See [here](https://pydata-sphinx-theme.readthedocs.io/en/stable/examples/kitchen-sink/admonitions.html#versionadded) for how they are rendered.
AutoGen v0.4 is a rewrite of AutoGen from the ground up to create a more robust,
6
+
scalable, easier to use, cross-language library for building AI Agents.
7
+
Some key features include asynchronous messaging, support for scalable distributed agents,
8
+
modular extensible design (bring your own agents, implement behaviors however you like),
9
+
cross-language support, improved observability, and full typing integration.
10
+
It is a breaking change.
11
+
12
+
### Why these changes?
13
+
14
+
We listened to our AutoGen users, learned from what was working, and adapted to fix what wasn't.
15
+
We brought together wide-ranging teams working on many different types of AI Agents
16
+
and collaborated to design an improved framework with a more flexible
17
+
programming model and better scalability.
18
+
19
+
### Is this project still maintained?
20
+
21
+
We want to reaffirm our commitment to supporting both the original version of AutoGen (0.2) and the redesign (0.4). AutoGen 0.4 is still work-in-progress, and we shared the code now to build with the community. There are no plans to deprecate the original AutoGen anytime soon, and both versions will be actively maintained.
22
+
23
+
### Who should use it 0.4?
24
+
25
+
This code is still experimental, so expect changes and bugs while we work towards a stable 0.4 release. We encourage early adopters to
26
+
try it out, give us feedback, and contribute.
27
+
For those looking for a stable version we recommend to continue using 0.2
28
+
29
+
### I'm using AutoGen 0.2, should I upgrade?
30
+
31
+
If you consider yourself an early adopter, you are comfortable making some
32
+
changes to your code, and are willing to try it out, then yes.
33
+
34
+
### How do I still use AutoGen 0.2?
35
+
36
+
AutoGen 0.2 can be installed with:
37
+
38
+
```sh
39
+
pip install autogen-agentchat~=0.2
40
+
```
41
+
42
+
### Will AutoGen Studio be supported in 0.4?
43
+
44
+
Yes, this is on the [roadmap](#roadmap).
45
+
Our current plan is to enable an implementation of AutoGen Studio
46
+
on the AgentChat high level API which implements a set of agent functionalities
47
+
(agents, teams, etc).
48
+
49
+
### How do I migrate?
50
+
51
+
For users familiar with AutoGen, the AgentChat library in 0.4 provides similar concepts.
52
+
We are working on a migration guide.
53
+
54
+
### Is 0.4 done?
55
+
56
+
We are still actively developing AutoGen 0.4. One exciting new feature is the emergence of new SDKs for .NET. The python SDKs are further ahead at this time but our goal is to achieve parity. We aim to add additional languages in future releases.
57
+
58
+
### What is happening next? When will this release be ready?
59
+
60
+
We are still working on improving the documentation, samples, and enhancing the code. We are hoping to release before the end of the year when things are ready.
61
+
62
+
### What is the history of this project?
63
+
64
+
The rearchitecture of the framework started with multiple Microsoft teams coming together
65
+
to address the gaps and learnings from AutoGen 0.2 - merging ideas from several predecessor projects.
66
+
The team worked on this internally for some time to ensure alignment before moving work back to the open in October 2024.
67
+
68
+
### What is the official channel for support?
69
+
70
+
Use GitHub [Issues](https://github.com/microsoft/autogen/issues) for bug reports and feature requests.
71
+
Use GitHub [Discussions](https://github.com/microsoft/autogen/discussions) for general questions and discussions.
72
+
73
+
### Do you use Discord for communications?
74
+
75
+
We are unable to use the old Discord for project discussions, many of the maintainers no longer have viewing or posting rights there. Therefore, we request that all discussions take place on <https://github.com/microsoft/autogen/discussions/> or the [new discord server](https://aka.ms/autogen-discord).
76
+
77
+
### What about forks?
78
+
79
+
<https://github.com/microsoft/autogen/> remains the only official repo for development and support of AutoGen.
80
+
We are aware that there are thousands of forks of AutoGen, including many for personal development and startups building with or on top of the library. We are not involved with any of these forks and are not aware of any plans related to them.
81
+
82
+
### What is the status of the license and open source?
83
+
84
+
Our project remains fully open-source and accessible to everyone. We understand that some forks use different licenses to align with different interests. We will continue to use the most permissive license (MIT) for the project.
85
+
86
+
### Can you clarify the current state of the packages?
87
+
88
+
Currently, we are unable to make releases to the `pyautogen` package via Pypi due to a change to package ownership that was done without our involvement. Additionally, we are moving to using multiple packages to align with the new design. Please see details [here](https://microsoft.github.io/autogen/dev/packages/index.html).
89
+
90
+
### Can I still be involved?
91
+
92
+
We are grateful to all the contributors to AutoGen 0.2 and we look forward to continuing to collaborate with everyone in the AutoGen community.
0 commit comments