[Fleet Execution] [Advanced Session Example]

[davideast]

Goal Reference

This issue was generated from .fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.

Objective

Create an advanced session example in the Jules TypeScript SDK documentation. This example should demonstrate more advanced features, such as interactive sessions, streaming activities, and handling artifacts.

Code-Level Diagnosis

Code path: packages/core/examples/advanced-session/
Mechanism: The packages/core/examples/advanced-session/ directory and its corresponding examples are entirely missing.
Root cause: The SDK lacks a runnable, practical example of an advanced session with streaming and artifacts.

Current Implementation

// Missing example

Proposed Implementation

Files to modify: Create packages/core/examples/advanced-session/index.ts and packages/core/examples/advanced-session/README.md. Update packages/core/README.md to link to the new example.

Integration (Before -> After)

--- a/packages/core/README.md
+++ b/packages/core/README.md
@@ -10,6 +10,10 @@
 Orchestrate complex, long-running coding tasks to an ephemeral cloud environment integrated with a GitHub repo.
 
+## Examples
+
+- [Basic Session](./examples/basic-session/README.md)
+- [Advanced Session](./examples/advanced-session/README.md)
+
 ## Send work to a Cloud based session

Test Scenarios

1. Run bun run index.ts (or equivalent) in the advanced-session directory -> The example runs successfully, streaming activities and displaying artifacts correctly without errors.
2. Follow the README.md instructions -> Instructions correctly guide a user to run the example.

Target Files

• packages/core/examples/advanced-session/index.ts
• packages/core/examples/advanced-session/README.md
• packages/core/README.md

Boundary Rules

Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.

---

Fleet Context

• Source: jules:session:14691557552061927599
• Link: https://jules.google.com/session/14691557552061927599