source stringclasses 1
value | repository stringclasses 1
value | file stringlengths 17 123 | label stringclasses 1
value | content stringlengths 6 6.94k |
|---|---|---|---|---|
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.SemanticKernel/SemanticKernelAgent-support-more-messages.md | autogen | @AutoGen.SemanticKernel.SemanticKernelAgent only supports the original `ChatMessageContent` type via `IMessage<ChatMessageContent>`. To support more AutoGen built-in message types like @AutoGen.Core.TextMessage, @AutoGen.Core.ImageMessage, @AutoGen.Core.MultiModalMessage, you can register the agent with @AutoGen.Semant... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.SemanticKernel/AutoGen-SemanticKernel-Overview.md | autogen | ## AutoGen.SemanticKernel Overview AutoGen.SemanticKernel is a package that provides seamless integration with Semantic Kernel. It provides the following agents: - @AutoGen.SemanticKernel.SemanticKernelAgent: A slim wrapper agent over `Kernel` that only support original `ChatMessageContent` type via `IMessage<ChatMess... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.SemanticKernel/Use-kernel-plugin-in-other-agents.md | autogen | In semantic kernel, a kernel plugin is a collection of kernel functions that can be invoked during LLM calls. Semantic kernel provides a list of built-in plugins, like [core plugins](https://github.com/microsoft/semantic-kernel/tree/main/dotnet/src/Plugins/Plugins.Core), [web search plugin](https://github.com/microsoft... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.SemanticKernel/SemanticKernelAgent-simple-chat.md | autogen | You can chat with @AutoGen.SemanticKernel.SemanticKernelAgent using both streaming and non-streaming methods and use native `ChatMessageContent` type via `IMessage<ChatMessageContent>`. The following example shows how to create an @AutoGen.SemanticKernel.SemanticKernelAgent and chat with it using non-streaming method:... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.SemanticKernel/SemanticKernelChatAgent-simple-chat.md | autogen | `AutoGen.SemanticKernel` provides built-in support for `ChatCompletionAgent` via @AutoGen.SemanticKernel.SemanticKernelChatCompletionAgent. By default the @AutoGen.SemanticKernel.SemanticKernelChatCompletionAgent only supports the original `ChatMessageContent` type via `IMessage<ChatMessageContent>`. To support more Au... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Gemini/Function-call-with-gemini.md | autogen | This example shows how to use @AutoGen.Gemini.GeminiChatAgent to make function call. This example is modified from [gemini-api function call example](https://ai.google.dev/gemini-api/docs/function-calling) To run this example, you need to have a project on Google Cloud with access to Vertex AI API. For more informatio... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Gemini/Overview.md | autogen | # AutoGen.Gemini Overview AutoGen.Gemini is a package that provides seamless integration with Google Gemini. It provides the following agent: - @AutoGen.Gemini.GeminiChatAgent: The agent that connects to Google Gemini or Vertex AI Gemini. It supports chat, multi-modal chat, and function call. AutoGen.Gemini also pro... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Gemini/Overview.md | autogen | Examples You can find more examples under the [gemini sample project](https://github.com/microsoft/autogen/tree/main/dotnet/samples/AutoGen.Gemini.Sample) |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Gemini/Image-chat-with-gemini.md | autogen | This example shows how to use @AutoGen.Gemini.GeminiChatAgent for image chat with Gemini model. To run this example, you need to have a project on Google Cloud with access to Vertex AI API. For more information please refer to [Google Vertex AI](https://cloud.google.com/vertex-ai/docs). > [!NOTE] > You can find the ... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Gemini/Chat-with-vertex-gemini.md | autogen | This example shows how to use @AutoGen.Gemini.GeminiChatAgent to connect to Vertex AI Gemini API and chat with Gemini model. To run this example, you need to have a project on Google Cloud with access to Vertex AI API. For more information please refer to [Google Vertex AI](https://cloud.google.com/vertex-ai/docs). >... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Gemini/Chat-with-google-gemini.md | autogen | This example shows how to use @AutoGen.Gemini.GeminiChatAgent to connect to Google AI Gemini and chat with Gemini model. To run this example, you need to have a Google AI Gemini API key. For how to get a Google Gemini API key, please refer to [Google Gemini](https://gemini.google.com/). > [!NOTE] > You can find the c... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Ollama/Chat-with-llava.md | autogen | This sample shows how to use @AutoGen.Ollama.OllamaAgent to chat with LLaVA model. To run this example, you need to have an Ollama server running aside and have `llava:latest` model installed. For how to setup an Ollama server, please refer to [Ollama](https://ollama.com/). > [!NOTE] > You can find the complete sampl... |
GitHub | autogen | autogen/dotnet/website/articles/AutoGen.Ollama/Chat-with-llama.md | autogen | This example shows how to use @AutoGen.Ollama.OllamaAgent to connect to Ollama server and chat with LLaVA model. To run this example, you need to have an Ollama server running aside and have `llama3:latest` model installed. For how to setup an Ollama server, please refer to [Ollama](https://ollama.com/). > [!NOTE] > ... |
GitHub | autogen | autogen/dotnet/samples/Hello/README.md | autogen | # Multiproject App Host for HelloAgent This is a [.NET Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview) App Host that starts up the HelloAgent project and the agents backend. Once the project starts up you will be able to view the telemetry and logs in the [Aspire Dashboard](https:/... |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgentState/README.md | autogen | # AutoGen 0.4 .NET Hello World Sample This [sample](Program.cs) demonstrates how to create a simple .NET console application that listens for an event and then orchestrates a series of actions in response. |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgentState/README.md | autogen | Prerequisites To run this sample, you'll need: [.NET 8.0](https://dotnet.microsoft.com/en-us/) or later. Also recommended is the [GitHub CLI](https://cli.github.com/). |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgentState/README.md | autogen | Instructions to run the sample ```bash # Clone the repository gh repo clone microsoft/autogen cd dotnet/samples/Hello dotnet run ``` |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgentState/README.md | autogen | Key Concepts This sample illustrates how to create your own agent that inherits from a base agent and listens for an event. It also shows how to use the SDK's App Runtime locally to start the agent and send messages. Flow Diagram: ```mermaid %%{init: {'theme':'forest'}}%% graph LR; A[Main] --> |"PublishEventAsyn... |
GitHub | autogen | autogen/dotnet/samples/Hello/Backend/README.md | autogen | # Backend Example This example demonstrates how to create a simple backend service for the agent runtime using ASP.NET Core. To Run it, simply run the following command in the terminal: ```bash dotnet run ``` Or you can run it using Visual Studio Code by pressing `F5`. |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgent/README.md | autogen | # AutoGen 0.4 .NET Hello World Sample This [sample](Program.cs) demonstrates how to create a simple .NET console application that listens for an event and then orchestrates a series of actions in response. |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgent/README.md | autogen | Prerequisites To run this sample, you'll need: [.NET 8.0](https://dotnet.microsoft.com/en-us/) or later. Also recommended is the [GitHub CLI](https://cli.github.com/). |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgent/README.md | autogen | Instructions to run the sample ```bash # Clone the repository gh repo clone microsoft/autogen cd dotnet/samples/Hello dotnet run ``` |
GitHub | autogen | autogen/dotnet/samples/Hello/HelloAgent/README.md | autogen | Key Concepts This sample illustrates how to create your own agent that inherits from a base agent and listens for an event. It also shows how to use the SDK's App Runtime locally to start the agent and send messages. Flow Diagram: ```mermaid %%{init: {'theme':'forest'}}%% graph LR; A[Main] --> |"PublishEventAsyn... |
GitHub | autogen | autogen/dotnet/samples/dev-team/README.md | autogen | # GitHub Dev Team with AI Agents Build a Dev Team using event driven agents. This project is an experiment and is not intended to be used in production. |
GitHub | autogen | autogen/dotnet/samples/dev-team/README.md | autogen | Background From a natural language specification, set out to integrate a team of AI agents into your team’s dev process, either for discrete tasks on an existing repo (unit tests, pipeline expansions, PRs for specific intents), developing a new feature, or even building an application from scratch. Starting from an e... |
GitHub | autogen | autogen/dotnet/samples/dev-team/README.md | autogen | Get it running Check [the getting started guide](./docs/github-flow-getting-started.md). |
GitHub | autogen | autogen/dotnet/samples/dev-team/README.md | autogen | Demo https://github.com/microsoft/azure-openai-dev-skills-orchestrator/assets/10728102/cafb1546-69ab-4c27-aaf5-1968313d637f |
GitHub | autogen | autogen/dotnet/samples/dev-team/README.md | autogen | Solution overview  |
GitHub | autogen | autogen/dotnet/samples/dev-team/README.md | autogen | How it works * User begins with creating an issue and then stateing what they want to accomplish, natural language, as simple or as detailed as needed. * Product manager agent will respond with a Readme, which can be iterated upon. * User approves the readme or gives feedback via issue comments. * Once the readme ... |
GitHub | autogen | autogen/dotnet/samples/dev-team/seed-memory/README.md | autogen | # TODO |
GitHub | autogen | autogen/dotnet/samples/dev-team/docs/github-flow-getting-started.md | autogen | ## Prerequisites - Access to gpt3.5-turbo or preferably gpt4 - [Get access here](https://learn.microsoft.com/en-us/azure/ai-services/openai/overview#how-do-i-get-access-to-azure-openai) - [Setup a Github app](#how-do-i-setup-the-github-app) - [Install the Github app](https://docs.github.com/en/apps/using-github-apps/i... |
GitHub | autogen | autogen/dotnet/samples/dev-team/docs/github-flow-getting-started.md | autogen | How do I run this locally? Codespaces are preset for this repo. For codespaces there is a 'free' tier for individual accounts. See: https://github.com/pricing Start by creating a codespace: https://docs.github.com/en/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository  to work with the Azure bits. `azd` is installed in the codespace. Let's start by logging in to Azure using ```bash azd auth login ``` After we've logged in, we need to cr... |
GitHub | autogen | autogen/docs/design/05 - Services.md | autogen | # AutoGen Services |
GitHub | autogen | autogen/docs/design/05 - Services.md | autogen | Overview Each AutoGen agent system has one or more Agent Workers and a set of services for managing/supporting the agents. The services and workers can all be hosted in the same process or in a distributed system. When in the same process communication and event delivery is in-memory. When distributed, workers commun... |
GitHub | autogen | autogen/docs/design/04 - Agent and Topic ID Specs.md | autogen | # Agent and Topic ID Specs This document describes the structure, constraints, and behavior of Agent IDs and Topic IDs. |
GitHub | autogen | autogen/docs/design/04 - Agent and Topic ID Specs.md | autogen | Agent ID ### Required Attributes #### type - Type: `string` - Description: The agent type is not an agent class. It associates an agent with a specific factory function, which produces instances of agents of the same agent `type`. For example, different factory functions can produce the same agent class but with dif... |
GitHub | autogen | autogen/docs/design/04 - Agent and Topic ID Specs.md | autogen | Topic ID ### Required Attributes #### type - Type: `string` - Description: Topic type is usually defined by application code to mark the type of messages the topic is for. - Constraints: UTF8 and only contain alphanumeric letters (a-z) and (0-9), or underscores (\_). A valid identifier cannot start with a number, or... |
GitHub | autogen | autogen/docs/design/03 - Agent Worker Protocol.md | autogen | # Agent Worker Protocol |
GitHub | autogen | autogen/docs/design/03 - Agent Worker Protocol.md | autogen | System architecture The system consists of multiple processes, each being either a _service_ process or a _worker_ process. Worker processes host application code (agents) and connect to a service process. Workers advertise the agents which they support to the service, so the service can decide which worker to place a... |
GitHub | autogen | autogen/docs/design/03 - Agent Worker Protocol.md | autogen | Worker protocol flow The worker protocol has three phases, following the lifetime of the worker: initialization, operation, and termination. ### Initialization When the worker process starts, it initiates a connection to a service process, establishing a bi-directional communication channel which messages are passed... |
GitHub | autogen | autogen/docs/design/02 - Topics.md | autogen | # Topics This document describes the semantics and components of publishing messages and subscribing to topics. |
GitHub | autogen | autogen/docs/design/02 - Topics.md | autogen | Overview Topics are used as the primitive to manage which agents receive a given published message. Agents subscribe to topics. There is an application defined mapping from topic to agent instance. These concepts intentionally map to the [CloudEvents](https://cloudevents.io/) specification. This allows for easy integ... |
GitHub | autogen | autogen/docs/design/02 - Topics.md | autogen | Identifiers A topic is identified by two components (called a `TopicId`): - [`type`](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#type) - represents the type of event that occurs, this is static and defined in code - SHOULD use reverse domain name notation to avoid naming conflicts. For examp... |
GitHub | autogen | autogen/docs/design/02 - Topics.md | autogen | Subscriptions Subscriptions define which agents receive messages published to a topic. Subscriptions are dynamic and can be added or removed at any time. A subscription defines two things: - Matcher func of type `TopicId -> bool`, telling us "does this subscription match this topic" - Mapper func of type `TopicId ->... |
GitHub | autogen | autogen/docs/design/02 - Topics.md | autogen | Message types Agents are able to handle certain types of messages. This is an internal detail of an agent's implementation. All agents in a channel will receive all messages, but will ignore messages that it cannot handle. > [!NOTE] > This might be revisited based on scaling and performance considerations. |
GitHub | autogen | autogen/docs/design/01 - Programming Model.md | autogen | # Programming Model Understanding your workflow and mapping it to agents is the key to building an agent system in AutoGen. The programming model is basically publish-subscribe. Agents subscribe to events they care about and also can publish events that other agents may care about. Agents may also have additonal asse... |
GitHub | autogen | autogen/docs/design/01 - Programming Model.md | autogen | Events Delivered as CloudEvents Each event in the system is defined using the [CloudEvents Specification](https://cloudevents.io/). This allows for a common event format that can be used across different systems and languages. In CloudEvents, each event has "Context Attributes" that must include: 1. *id* - A unique i... |
GitHub | autogen | autogen/docs/design/01 - Programming Model.md | autogen | Event Handlers Each agent has a set of event handlers, that are bound to a specific match against a CloudEvents *type*. Event Handlers could match against an exact type or match for a pattern of events of a particular level in the type heirarchy (eg: `com.Microsoft.AutoGen.Agents.System.*` for all Events in the `Syste... |
GitHub | autogen | autogen/docs/design/01 - Programming Model.md | autogen | Orchestrating Agents It is possible to build a functional and scalable agent system that only reacts to external events. In many cases, however, you will want to orchestrate the agents to achieve a specific goal or follow a pre-determined workflow. In this case, you will need to build an orchestrator agent that manage... |
GitHub | autogen | autogen/docs/design/01 - Programming Model.md | autogen | Built-in Event Types The AutoGen system comes with a set of built-in event types that are used to manage the system. These include: - *System Events* - Events that are used to manage the system itself. These include events for starting and stopping the Agents, sending messages to all agents, and other system-level ev... |
GitHub | autogen | autogen/docs/design/01 - Programming Model.md | autogen | Agent Contracts You may want to leverage more prescriptive agent behavior contracts, and AutoGen also includes base agents that implement different approaches to agent behavior, including layering request/response patterns on top of the event-driven model. For an example of this see the ChatAgents in the Python exampl... |
GitHub | autogen | autogen/.github/PULL_REQUEST_TEMPLATE.md | autogen | <!-- Thank you for your contribution! Please review https://microsoft.github.io/autogen/docs/Contribute before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> |
GitHub | autogen | autogen/.github/PULL_REQUEST_TEMPLATE.md | autogen | Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> |
GitHub | autogen | autogen/.github/PULL_REQUEST_TEMPLATE.md | autogen | Related issue number <!-- For example: "Closes #1234" --> |
GitHub | autogen | autogen/.github/PULL_REQUEST_TEMPLATE.md | autogen | Checks - [ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally. - [ ] I've added tests (if relevant) corresponding to the changes introduced in this PR. - [ ] I've made sure all au... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.