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
To see what we are working on and what we plan to work on, please check our
30
-
[Roadmap Issues](https://aka.ms/autogen-roadmap).
29
+
It is important to use `uv` when running CI checks locally as it ensures that the correct dependencies and versions are used.
30
+
31
+
Please follow the instructions [here](./python/README.md#setup) to get set up.
32
+
33
+
For common tasks that are helpful during development and run in CI, see [here](./python/README.md#common-tasks).
34
+
35
+
## Roadmap
36
+
37
+
We use GitHub issues and milestones to track our roadmap. You can view the upcoming milestones [here]([Roadmap Issues](https://aka.ms/autogen-roadmap).
38
+
39
+
## Versioning
40
+
41
+
The set of `autogen-*` packages are generally all versioned together. When a change is made to one package, all packages are updated to the same version. This is to ensure that all packages are in sync with each other.
42
+
43
+
We will update verion numbers according to the following rules:
44
+
45
+
- Increase minor version (0.X.0) upon breaking changes
46
+
- Increase patch version (0.0.X) upon new features or bug fixes
47
+
48
+
## Release process
49
+
50
+
1. Create a PR that updates the version numbers across the codebase ([example](https://github.com/microsoft/autogen/pull/4359))
51
+
2. The docs CI will fail for the PR, but this is expected and will be resolved in the next step
52
+
2. After merging the PR, create and push a tag that corresponds to the new verion. For example, for `0.4.0.dev7`:
53
+
-`git tag 0.4.0.dev7 && git push origin 0.4.0.dev7`
54
+
3. Restart the docs CI by finding the failed [job corresponding to the `push` event](https://github.com/microsoft/autogen/actions/workflows/docs.yml) and restarting all jobs
55
+
4. Run [this](https://github.com/microsoft/autogen/actions/workflows/single-python-package.yml) workflow for each of the packages that need to be released and get an approval for the release for it to run
56
+
57
+
## Triage process
58
+
59
+
To help ensure the health of the project and community the AutoGen committers have a weekly triage process to ensure that all issues and pull requests are reviewed and addressed in a timely manner. The following documents the responsibilites while on triage duty:
60
+
61
+
- Issues
62
+
- Review all new issues - these will be tagged with [`needs-triage`](https://github.com/microsoft/autogen/issues?q=is%3Aissue%20state%3Aopen%20label%3Aneeds-triage).
63
+
- Apply appropriate labels:
64
+
- One of `proj-*` labels based on the project the issue is related to
65
+
-`documentation`: related to documentation
66
+
-`x-lang`: related to cross language functionality
67
+
-`dotnet`: related to .NET
68
+
- Add the issue to a relevant milestone if necessary
69
+
- If you can resolve the issue or reply to the OP please do.
70
+
- If you cannot resolve the issue, assign it to the appropriate person.
71
+
- If awaiting a reply add the tag `awaiting-op-response` (this will be auto removed when the OP replies).
72
+
- Bonus: there is a backlog of old issues that need to be reviewed - if you have time, review these as well and close or refresh as many as you can.
73
+
- PRs
74
+
- The UX on GH flags all recently updated PRs. Draft PRs can be ignored, otherwise review all recently updated PRs.
75
+
- If a PR is ready for review and you can provide one please go ahead. If you cant, please assign someone. You can quickly spin up a codespace with the PR to test it out.
76
+
- If a PR is needing a reply from the op, please tag it `awaiting-op-response`.
77
+
- If a PR is approved and passes CI, its ready to merge, please do so.
78
+
- If it looks like there is a possibly transient CI failure, re-run failed jobs.
79
+
- Discussions
80
+
- Look for recently updated discussions and reply as needed or find someone on the team to reply.
81
+
- Security
82
+
- Look through any securty alerts and file issues or dismiss as needed.
> - (11/14/24) ⚠️ In response to a number of asks to clarify and distinguish between official AutoGen and its forks that created confusion, we issued a [clarification statement](https://github.com/microsoft/autogen/discussions/4217).
14
16
> - (10/13/24) Interested in the standard AutoGen as a prior user? Find it at the actively-maintained *AutoGen*[0.2 branch](https://github.com/microsoft/autogen/tree/0.2) and `autogen-agentchat~=0.2` PyPi package.
15
17
> - (10/02/24) [AutoGen 0.4](https://microsoft.github.io/autogen/dev) is a from-the-ground-up rewrite of AutoGen. Learn more about the history, goals and future at [this blog post](https://microsoft.github.io/autogen/blog). We’re excited to work with the community to gather feedback, refine, and improve the project before we officially release 0.4. This is a big change, so AutoGen 0.2 is still available, maintained, and developed in the [0.2 branch](https://github.com/microsoft/autogen/tree/0.2).
18
+
> -*[Join us for Community Office Hours](https://github.com/microsoft/autogen/discussions/4059)* We will host a weekly open discussion to answer questions, talk about Roadmap, etc.
16
19
17
20
AutoGen is an open-source framework for building AI agent systems.
18
21
It simplifies the creation of event-driven, distributed, scalable, and resilient agentic applications.
Copy file name to clipboardexpand all lines: docs/design/04 - Agent and Topic ID Specs.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This document describes the structure, constraints, and behavior of Agent IDs an
34
34
35
35
- Type: `string`
36
36
- Description: Topic type is usually defined by application code to mark the type of messages the topic is for.
37
-
- Constraints: UTF8 and only contain alphanumeric letters (a-z) and (0-9), or underscores (\_). A valid identifier cannot start with a number, or contain any spaces.
37
+
- Constraints: UTF8 and only contain alphanumeric letters (a-z) and (0-9), ':', '=', or underscores (\_). A valid identifier cannot start with a number, or contain any spaces.
//TODO: we should consider having constraints on the namespace or at least migrate all our examples to use well typed namesspaces like com.microsoft.autogen/hello/HelloAgents etc
Copy file name to clipboardexpand all lines: python/packages/autogen-agentchat/src/autogen_agentchat/agents/_assistant_agent.py
+3-3
Original file line number
Diff line number
Diff line change
@@ -82,13 +82,13 @@ def _handoff_tool() -> str:
82
82
classAssistantAgent(BaseChatAgent):
83
83
"""An agent that provides assistance with tool use.
84
84
85
-
It responds with a StopMessage when 'terminate' is detected in the response.
86
-
87
85
Args:
88
86
name (str): The name of the agent.
89
87
model_client (ChatCompletionClient): The model client to use for inference.
90
88
tools (List[Tool | Callable[..., Any] | Callable[..., Awaitable[Any]]] | None, optional): The tools to register with the agent.
91
-
handoffs (List[Handoff | str] | None, optional): The handoff configurations for the agent, allowing it to transfer to other agents by responding with a HandoffMessage.
89
+
handoffs (List[Handoff | str] | None, optional): The handoff configurations for the agent,
90
+
allowing it to transfer to other agents by responding with a :class:`HandoffMessage`.
91
+
The transfer is only executed when the team is in :class:`~autogen_agentchat.teams.Swarm`.
92
92
If a handoff is a string, it should represent the target agent's name.
93
93
description (str, optional): The description of the agent.
94
94
system_message (str, optional): The system message for the model.
0 commit comments