---
type: "post"
id: "managed-deep-agents-0-8-ships-http-channels-a983f1"
slug: "managed-deep-agents-0-8-ships-http-channels-a983f1"
title: "Managed Deep Agents 0.8 ships HTTP channels: agents can take requests from any webhook, not just Slack."
description: "Thesis: Managed Deep Agents 0.8 broadens agent access beyond Slack by adding HTTP channels, while making identity and memory scope part of the production integration design."
retrieval_nugget: "Thesis: Managed Deep Agents 0.8 broadens agent access beyond Slack by adding HTTP channels, while making identity and memory scope part of the production integration design."
published_at: "2026-09-30"
updated_at: "2026-09-30"
record_date: "2026-09-30"
date_kind: "published_at"
topics: []
source_urls: ["https://www.langchain.com/blog/langsmith-managed-deep-agents-whats-new"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:managed-deep-agents-0-8-ships-http-channels-a983f1"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:5f3fa966540ed9dbed04b94f74caa0a36d302e85db0bb3ddfbdfaa28a270a51b","reviewed_at":"2026-09-30T17:04:01.564Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":2,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Managed Deep Agents 0.8 broadens agent access beyond Slack by adding HTTP channels, while making identity and memory scope part of the production integration design.","observed_facts":[{"text":"LangChain says the release adds HTTP channels for use in internal tools, customer portals, and support systems.","source_urls":["https://www.langchain.com/blog/langsmith-managed-deep-agents-whats-new"]},{"text":"The post says agent memory is shared by deployment users, while user memory is keyed to the caller’s authenticated identity; its stated HTTP default denies user-level memory.","source_urls":["https://www.langchain.com/blog/langsmith-managed-deep-agents-whats-new"]},{"text":"The announcement lists user-owned credentials, Slack file transfer, and built-in web search powered by Parallel.","source_urls":["https://www.langchain.com/blog/langsmith-managed-deep-agents-whats-new"]}],"mechanism":"An HTTP channel supplies an entry point for requests from systems that can send webhooks. The caller’s authenticated identity can then determine which credentials and memory layer apply; the documented default keeps personal memory unavailable in HTTP runs unless teams configure otherwise. This creates a boundary between shared agent context and caller-specific context rather than treating all incoming requests alike.","why_now":"The 0.8 release makes HTTP channels an announced option for teams bringing agents into product and support surfaces, so the accompanying identity and memory defaults matter at integration time.","implications":["Teams can consider webhook-capable product surfaces as agent entry points, not only Slack.","Implementers need to decide whether HTTP runs should use caller-specific memory and how caller identity is authenticated."],"evidence_boundary":"These details come from LangChain’s release announcement; they establish announced capabilities and stated defaults, not independent validation of security, operational reliability, adoption, or performance.","watch_conditions":["Whether LangChain documents configuration and identity-handling requirements for enabling user-level memory on HTTP runs.","Whether the company or customers publish production examples showing HTTP channel deployment and its operational constraints."],"related_records":[],"new_branch_reason":"No prior New Runtime record is supplied; this release is therefore opened as a distinct analytical record without asserting a relationship to the coverage matches."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/managed-deep-agents-0-8-ships-http-channels-a983f1/","markdown":"https://newruntime.com/posts/managed-deep-agents-0-8-ships-http-channels-a983f1.md","json":"https://newruntime.com/posts/managed-deep-agents-0-8-ships-http-channels-a983f1.json"}
---

# Managed Deep Agents 0.8 ships HTTP channels: agents can take requests from any webhook, not just Slack.

## Retrieval answer

Thesis: Managed Deep Agents 0.8 broadens agent access beyond Slack by adding HTTP channels, while making identity and memory scope part of the production integration design.

Thesis: Managed Deep Agents 0.8 broadens agent access beyond Slack by adding HTTP channels, while making identity and memory scope part of the production integration design.

Observed facts: LangChain says the release adds HTTP channels for use in internal tools, customer portals, and support systems. The post also says agent memory is shared by deployment users, while user memory is keyed to the caller’s authenticated identity; its stated HTTP default denies user-level memory. The announcement additionally lists user-owned credentials, Slack file transfer, and built-in web search powered by Parallel.

Mechanism: An HTTP channel supplies an entry point for requests from systems that can send webhooks. The caller’s authenticated identity can then determine which credentials and memory layer apply; the documented default keeps personal memory unavailable in HTTP runs unless teams configure otherwise. This creates a boundary between shared agent context and caller-specific context rather than treating all incoming requests alike.

Why now: The 0.8 release makes HTTP channels an announced option for teams bringing agents into product and support surfaces, so the accompanying identity and memory defaults matter at integration time.

Implications:
- Teams can consider webhook-capable product surfaces as agent entry points, not only Slack.
- Implementers need to decide whether HTTP runs should use caller-specific memory and how caller identity is authenticated.

Evidence boundary: These details come from LangChain’s release announcement; they establish announced capabilities and stated defaults, not independent validation of security, operational reliability, adoption, or performance.

Watch conditions:
- Whether LangChain documents configuration and identity-handling requirements for enabling user-level memory on HTTP runs.
- Whether the company or customers publish production examples showing HTTP channel deployment and its operational constraints.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)