-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Open
Feature
10 / 1210 of 12 issues completed
Copy link
Labels
.NETIssue or Pull requests regarding .NET codeIssue or Pull requests regarding .NET codeSK-H2-PlanningIssues tagged with this label are listed in SK H2 Planning loopIssues tagged with this label are listed in SK H2 Planning loopmsft.ext.aiRelated to Microsoft.Extensions.AIRelated to Microsoft.Extensions.AIsk team issueA tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Description
As a developer I can use the M.E.AI abstractions with SK and all existing SK functionality will work e.g. prompt functions, chat history parsing, auto invocation filters, AI service selection, telemetry, chat history serialisation, ...
As a developer who is using the SK AI abstractions I can switch to use the M.E.AI abstractions by following the guidelines and maintain all of the functionality I had with the SK AI abstractions e.g. prompt functions, chat history parsing, auto invocation filters, AI service selection, telemetry, chat history serialisation, ...
The ADR must detail how existing SK specific functionality (including Agents) will work when a developer switches to using the M.E.AI abstractions.
Reactions are currently unavailable
Sub-issues
Metadata
Metadata
Assignees
Labels
.NETIssue or Pull requests regarding .NET codeIssue or Pull requests regarding .NET codeSK-H2-PlanningIssues tagged with this label are listed in SK H2 Planning loopIssues tagged with this label are listed in SK H2 Planning loopmsft.ext.aiRelated to Microsoft.Extensions.AIRelated to Microsoft.Extensions.AIsk team issueA tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Type
Projects
Status
Sprint: In Progress