mirror of
https://github.com/github/awesome-copilot.git
synced 2026-02-20 10:25:13 +00:00
All 5 Go recipes and their markdown docs used incorrect API patterns that don't match the real github.com/github/copilot-sdk/go v0.1.23: - copilot.NewClient() -> copilot.NewClient(nil) (*ClientOptions param) - client.Start() -> client.Start(ctx) (context.Context required) - copilot.SessionConfig -> &copilot.SessionConfig (pointer required) - session.On(func(event copilot.Event)) -> session.On(func(event copilot.SessionEvent)) - Type assertions -> event.Type string check + *event.Data.Content deref - session.WaitForIdle() -> session.SendAndWait(ctx, ...) (WaitForIdle doesn't exist) - copilot.SystemMessage -> copilot.SystemMessageConfig All 5 recipes verified to compile against SDK v0.1.23.
2.7 KiB
2.7 KiB
Working with Multiple Sessions
Manage multiple independent conversations simultaneously.
Runnable example: recipe/multiple-sessions.go
go run recipe/multiple-sessions.go
Example scenario
You need to run multiple conversations in parallel, each with its own context and history.
Go
package main
import (
"context"
"fmt"
"log"
copilot "github.com/github/copilot-sdk/go"
)
func main() {
ctx := context.Background()
client := copilot.NewClient(nil)
if err := client.Start(ctx); err != nil {
log.Fatal(err)
}
defer client.Stop()
// Create multiple independent sessions
session1, err := client.CreateSession(ctx, &copilot.SessionConfig{Model: "gpt-5"})
if err != nil {
log.Fatal(err)
}
defer session1.Destroy()
session2, err := client.CreateSession(ctx, &copilot.SessionConfig{Model: "gpt-5"})
if err != nil {
log.Fatal(err)
}
defer session2.Destroy()
session3, err := client.CreateSession(ctx, &copilot.SessionConfig{Model: "claude-sonnet-4.5"})
if err != nil {
log.Fatal(err)
}
defer session3.Destroy()
// Each session maintains its own conversation history
session1.Send(ctx, copilot.MessageOptions{Prompt: "You are helping with a Python project"})
session2.Send(ctx, copilot.MessageOptions{Prompt: "You are helping with a TypeScript project"})
session3.Send(ctx, copilot.MessageOptions{Prompt: "You are helping with a Go project"})
// Follow-up messages stay in their respective contexts
session1.Send(ctx, copilot.MessageOptions{Prompt: "How do I create a virtual environment?"})
session2.Send(ctx, copilot.MessageOptions{Prompt: "How do I set up tsconfig?"})
session3.Send(ctx, copilot.MessageOptions{Prompt: "How do I initialize a module?"})
}
Custom session IDs
Use custom IDs for easier tracking:
session, err := client.CreateSession(ctx, &copilot.SessionConfig{
SessionID: "user-123-chat",
Model: "gpt-5",
})
if err != nil {
log.Fatal(err)
}
fmt.Println(session.SessionID) // "user-123-chat"
Listing sessions
sessions, err := client.ListSessions(ctx)
if err != nil {
log.Fatal(err)
}
for _, sessionInfo := range sessions {
fmt.Printf("Session: %s\n", sessionInfo.SessionID)
}
Deleting sessions
// Delete a specific session
if err := client.DeleteSession(ctx, "user-123-chat"); err != nil {
log.Printf("Failed to delete session: %v", err)
}
Use cases
- Multi-user applications: One session per user
- Multi-task workflows: Separate sessions for different tasks
- A/B testing: Compare responses from different models