docs: restructure research agent notebook

[PedramNavid]

Reorganized the notebook to improve pedagogical flow and add detailed guidance:

• Added introduction explaining why research agents are ideal agentic use cases
• Included prerequisites section with required knowledge and setup instructions
• Expanded stateless query example with output visualization and detailed explanations
• Clarified when to use stateless vs stateful agent patterns
• Enhanced production-ready improvements section with three key enhancements
• Added stateful agent example using ClaudeSDKClient with conversation memory
• Improved conclusion with clear learning outcomes and next steps
• Updated kernel specification to match current environment

Pull Request

Description

Type of Change

• New cookbook
• Bug fix (fixes an issue in existing cookbook)
• Documentation update
• Code quality improvement (refactoring, optimization)
• Dependency update
• Other (please describe):

Cookbook Checklist (if applicable)

• Cookbook has a clear, descriptive title
• Includes a problem statement or use case description
• Code is well-commented and easy to follow
• Includes expected outputs or results

Testing

• I have tested this cookbook/change locally
• All cells execute without errors

Additional Context

---

Note: Pull requests that do not follow these guidelines or lack sufficient detail may be closed. This helps us maintain high-quality, useful cookbooks for the community. If you're unsure about any requirements, please open an issue to discuss before submitting a PR.

[github-actions]

Summary

Status	Count
🔍 Total	5
✅ Successful	0
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	1
❓ Unknown	0
🚫 Errors	4
⛔ Unsupported	0

Errors per input

Errors in temp_md/00_The_one_liner_research_agent.md

• [ERROR] file:///home/runner/work/claude-cookbooks/claude-cookbooks/temp_md/01_The_chief_of_staff_agent.ipynb | Cannot find file: File not found. Check if file exists and path is correct
• [200] https://docs.claude.com/en/docs/claude-code/settings#tools-available-to-claude | Rejected status code (this depends on your "accept" configuration): OK
• [200] https://github.com/anthropics/anthropic-cookbook/tree/main/patterns/agents/prompts | Rejected status code (this depends on your "accept" configuration): OK
• [200] https://www.anthropic.com/engineering/building-effective-agents | Rejected status code (this depends on your "accept" configuration): OK
  Full Github Actions output

[github-actions]

Model Check Results ✅

I've reviewed the model usage in claude_agent_sdk/00_The_one_liner_research_agent.ipynb against the current public Claude models list.

Summary: All Good!

All model references use valid, current public model identifiers.

Model References Found:

• claude-sonnet-4-5 - Used 3 times (lines 99, 140, 361)

Validation:

✅ claude-sonnet-4-5 is a valid current model alias

• Full ID: claude-sonnet-4-5-20250929
• Status: Latest and recommended - "Our smartest model for complex agents and coding"
• This is the recommended alias format ending in -latest for better maintainability

Recommendations:

None needed! The notebook already follows best practices by using the -latest alias format (claude-sonnet-4-5) rather than the dated version ID. This ensures the code will automatically use the latest Sonnet 4.5 model without requiring updates.

No Issues Found:

• ✅ No deprecated models detected
• ✅ No internal/non-public model names
• ✅ Already using recommended -latest alias format

[zealoushacker]

Thanks for updating this.

Recommend adding a checkbox to the PR template for adding a visual demo video of any new or modified cookbooks, showcasing the changes, at least until we have a CI workflow that publishes them to HTML for easy review.

Otherwise, a review requires pulling down the PR and looking at the new cookbook trying to match the diff to the updates in the cookbook.

[PedramNavid]

Thanks for updating this.

Recommend adding a checkbox to the PR template for adding a visual demo video of any new or modified cookbooks, showcasing the changes, at least until we have a CI workflow that publishes them to HTML for easy review.

Otherwise, a review requires pulling down the PR and looking at the new cookbook trying to match the diff to the updates in the cookbook.

great idea. i was looking at this too.