docs: session isolation (#6846)

documentation/docs/guides/acp-clients.md

@@ -18,6 +18,7 @@ The client manages the goose lifecycle automatically, including:
 - **Initialization**: The client runs the `goose acp` command to initialize the connection
 - **Communication**: The client communicates with goose over stdio using JSON-RPC
 - **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
 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

@@ -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
 
 When running goose in a CI/CD environment, keep these security practices in mind: