tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

docs: session isolation (#6846)

Browse Source
This commit is contained in:
dianed-square
2026-01-30 11:44:18 -08:00
committed by GitHub
parent 21b0178884
commit 3d4a20f5c1
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/guides/acp-clients.md
+1
View File
@@ -18,6 +18,7 @@ The client manages the goose lifecycle automatically, including:
- **Initialization**: The client runs the `goose acp` command to initialize the connection - **Initialization**: The client runs the `goose acp` command to initialize the connection
- **Communication**: The client communicates with goose over stdio using JSON-RPC - **Communication**: The client communicates with goose over stdio using JSON-RPC
- **Multiple Sessions**: The client manages multiple concurrent goose conversations simultaneously - **Multiple Sessions**: The client manages multiple concurrent goose conversations simultaneously
- **Session Isolation**: Each session maintains its own isolated state, including conversation history, agent context, and extension configurations, allowing concurrent sessions to run without interference
:::info Session Persistence :::info Session Persistence
ACP sessions are saved to goose's session history where you can access and manage them using goose. Access to session history in ACP clients might vary. ACP sessions are saved to goose's session history where you can access and manage them using goose. Access to session history in ACP clients might vary.
documentation/docs/tutorials/cicd.md
+8
View File
@@ -230,6 +230,14 @@ This is just one example of what's possible. Feel free to modify your GitHub Act
--- ---
## Running Multiple goose Instances in Parallel
goose supports running multiple concurrent sessions with isolated state, making it safe to run parallel jobs in your CI/CD pipeline. Each goose instance maintains its own conversation history, agent context, and extension configurations without interference.
This enables use cases like matrix builds across different environments or processing multiple components simultaneously.
---
## Security Considerations ## Security Considerations
When running goose in a CI/CD environment, keep these security practices in mind: When running goose in a CI/CD environment, keep these security practices in mind: