Amazon SageMaker Data Agent now supports conversation history
Data analysts can now resume prior AI-assisted sessions without rebuilding context, saving time across complex, multi-session analytical workflows.
View original announcement →Visual Summary
graph TD
A{{SageMaker Data Agent\nConversation History}}:::announced
B(SageMaker Unified Studio):::compute
C([Notebook Workflows]):::feature
D([Query Editor]):::feature
E([Auto-generated Titles\n& Timestamps]):::feature
F((Data Practitioners)):::external
G(Data Catalogs):::storage
H([Code Generation]):::feature
F ==>|"resumes sessions"| A
A -->|"embedded in"| B
B -->|"supports"| C
B -->|"supports"| D
A -->|"provides"| E
A -->|"generates"| H
A -.->|"integrates with"| G
C -->|"preserves context"| A
D -->|"preserves context"| A
classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold
classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0
classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32
classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100
classDef external fill:#f5f5f5,stroke:#616161,color:#616161
What's New
Amazon SageMaker Data Agent, embedded within SageMaker Unified Studio, now persists conversation history across analytical sessions, allowing data practitioners to resume prior interactions without losing context. Users can access a scrollable list of past conversations via a clock icon in the chat panel header, with each session identified by an auto-generated title and timestamp. This update applies to both Notebook and Query Editor workflows, covering code generation, error diagnosis, and multi-step data analysis use cases.
How It Works
- Conversation history panel: A clock icon in the chat panel header opens a scrollable list of all past conversations, each tagged with an auto-generated title and timestamp for quick identification.
- Session continuity: When a user selects a prior conversation, the full context—including agent-generated code, prompts, and responses—is restored, enabling seamless resumption of complex workflows.
- Scope of coverage: History is preserved across both Notebook and Query Editor environments within SageMaker Unified Studio, covering code generation, SQL query building, and troubleshooting interactions.
- Agent capabilities: The underlying SageMaker Data Agent generates code and execution plans from natural language prompts, integrates with data catalogs and business metadata, and supports IAM and IAM Identity Center (IdC) domains.
- No manual saving required: Conversations are automatically persisted without requiring users to explicitly save or export sessions, reducing friction in day-to-day workflows.
Why It's Important
- Eliminates context rebuilding: Data practitioners previously had to re-explain analytical context at the start of each session; conversation history removes this overhead entirely, saving meaningful time on complex, iterative projects.
- Supports multi-step analyses: Long-running analytical workflows that span multiple sessions—such as iterative model feature engineering or incremental SQL query refinement—can now progress without regression.
- Reduces rework on concurrent projects: Teams juggling multiple projects can switch between workstreams and return to any prior conversation without losing the thread, improving throughput and focus.
- Improves troubleshooting continuity: Past error diagnosis interactions are preserved, so users can reference prior fixes and avoid repeating debugging cycles on recurring issues.
- Accelerates onboarding and collaboration: New team members or collaborators can review prior agent interactions to understand analytical decisions and code rationale, improving knowledge transfer.
How It's Different
- Persistent vs. ephemeral sessions: Unlike typical AI chat assistants embedded in IDEs that reset on session close, SageMaker Data Agent now retains full conversation history indefinitely across sessions.
- Integrated with analytical tooling: History is preserved natively within Notebooks and Query Editor—not in a separate interface—keeping the context directly alongside the code and queries it generated.
- Auto-generated metadata: Conversations are automatically titled and timestamped without user intervention, contrasting with tools that require manual naming or bookmarking to organize past sessions.
- Data catalog awareness: The agent's history includes interactions that leveraged data catalog and business metadata context, meaning resumed sessions retain awareness of previously referenced datasets and schemas.
- Unified environment: Because SageMaker Unified Studio consolidates notebooks, SQL editors, and AI assistance in one platform, conversation history spans all these modalities rather than being siloed per tool.
When to Prefer It
- Multi-day or multi-sprint analyses: When an analytical project spans several work sessions and requires iterative refinement of code or queries, conversation history ensures no context is lost between sittings.
- Concurrent project management: When data practitioners are actively working on multiple projects simultaneously and need to context-switch frequently without losing progress on any individual workstream.
- Recurring troubleshooting scenarios: When debugging persistent or intermittent data pipeline errors, having access to prior diagnostic conversations accelerates root cause identification.
- Team handoffs and code reviews: When a data engineer or analyst needs to hand off work to a colleague, prior agent conversations serve as a natural audit trail of analytical decisions and generated code.
- Complex SQL or ML workflow development: When building multi-step SQL transformations or ML feature pipelines that require incremental iteration, resuming from a prior conversation avoids redundant re-prompting.
- Regulated or auditable environments: When analytical workflows require documentation of how code or logic was derived, conversation history provides a traceable record of agent interactions.
Availability
- GA status: This feature is generally available as of June 3, 2026, with no preview or beta designation indicated.
- Supported regions: Available in all 15 AWS regions where SageMaker Unified Studio is currently supported: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Europe (London), Europe (Paris), Europe (Stockholm), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Mumbai), South America (São Paulo), and Canada (Central).
- Prerequisites: Requires an open notebook or querybook in SageMaker Unified Studio and access to SageMaker Data Agent features within the domain; supported in both IAM and IAM Identity Center (IdC) domains.
- Pricing: No separate pricing for conversation history was announced; it is part of the SageMaker Data Agent feature set within SageMaker Unified Studio—standard SageMaker usage costs apply.
- Limitations: No explicit retention limits or maximum conversation counts were disclosed in the announcement documentation.
