惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
The GitHub Blog
The GitHub Blog
A
About on SuperTechFans
P
Proofpoint News Feed
G
Google Developers Blog
Stack Overflow Blog
Stack Overflow Blog
IT之家
IT之家
Microsoft Security Blog
Microsoft Security Blog
F
Fortinet All Blogs
人人都是产品经理
人人都是产品经理
博客园 - 叶小钗
C
Check Point Blog
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
月光博客
月光博客
美团技术团队
D
Docker
博客园 - Franky
Y
Y Combinator Blog
大猫的无限游戏
大猫的无限游戏
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - 【当耐特】
罗磊的独立博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报

LangChain Forum - Topics tagged python-help

Llama-server process has terminated: invalid argument --load-mode with Ollama client 0.32.6 and langchain-ollama 1.1.0 Langchain Certified Agent Engineer Exam - Exam link not received and no response Null-drift: A bare-metal O(1) Memory Store for continuous LangGraph agents Clarification needed: Assistant config vs context and graph initialization Proposal: a small local helper for readable run traces via PR Proxy Authentication Required 407 What is the right way to dynamically create and run a graph? Re-Implement claude code's dynamic workflow using langchian & deepagents How to define a correct state for multi-agent system Response Format Groq Model Pydantic I hope to get some recommendations for practical skills Interrupt does not work correctly in LangGraph The Qwen3.6b model in fireworks through initchatmodel reporting hugely inflated tokens For parallel execution in Node, should i use the functional API? Potential Enhancement: Django-Managed PostgresSaver Pre-interrupt() code re-runs on resume — anti-pattern, or is there a sanctioned way to detect resume? Interrupt parallel branch execution Best practices for self-hosting LangGraph Server OSS without LangGraph keys Dynamically Enabling/Disabling Graphs in a LangGraph Server at Runtime LangGraph thread copy can take 12+ minutes: recommended production pattern? Will DeltaChannel be the default for AgentState.messages, or expected to stay opt-in? Proposal: additional docs for implementing custom DB checkpointers or a guide on generic base checkpointer Prompt_cache_retention: '24h' supported in langchain agents and where to provide it, inside invoke or while creating client? Could RAG pipelines realistically cause deployment timeouts, is Render suitable for first-time RAG deployments? How do I use langchain_postgres' init_vectorstore_table correctly? Proposal: Graph-wide default error handler for StateGraph (fallback for nodes without error_handler) Support timedelta for CachePolicy.ttl, consistent with TimeoutPolicy Anyone confirms this issue that deepagent ui streaming is disturb by update in deepagent or bug issue Best Stack for Building AI Applications Seeking help regarding the connection between Websocket and tool calls
LOGIC.md — declarative reasoning contracts that compile t...
SingleSource · 2026-04-20 · via LangChain Forum - Topics tagged python-help
Been building a declarative spec format for multi-agent reasoning, and the LangGraph adapter is the most developed integration. Posting here for feedback from people running StateGraph systems in production. What LOGIC.md is A YAML file that declares step DAGs, output contracts, quality gates, tool permissions, and fallback chains. Framework-agnostic, compiles to LangGraph today (CrewAI and AutoGen planned). Why this might matter for LangGraph users Right now, if you want StateGraph to enforce output contracts, quality gates, or tool permissions, you write it imperatively — validation logic in each node function, retry logic scattered across the graph. With LOGIC.md you declare it once: yaml contracts: outputs: sources: { type: array, items: { type: object } } quality_gates: post_output: - check: "outputs.sources.length > 0" action: retry max_retries: 3 The adapter compiles this to StateGraph node definitions with: Type-validated state schemas Pre/post node hooks for contract enforcement Automatic retry logic for failed quality gates Per-node tool permission checks Fallback edge routing typescript import { compile_to_langgraph } from "@logic-md/adapters/langgraph"; const spec = parse(markdownContent); const graph_builder = compile_to_langgraph(spec); const graph = graph_builder.compile(); // graph is a LangGraph StateGraph with LOGIC.md contracts baked in Adapter state (honest) Proof of concept. Core node compilation works. Quality gates and tool permissions are stubbed. Needs real workflows to validate the API — I built it in isolation so there are almost certainly design issues a production LangGraph user would catch immediately. What I’m looking for feedback on Does the LOGIC.md data model fit how you actually build LangGraph workflows, or are there primitives missing? For those running LangGraph at scale — what do you currently do for output contracts and quality gates? Imperative code, or something else? Streaming: how should declarative contracts behave when reasoning happens incrementally? Open design question. Are there LangGraph patterns you’d want the adapter tested against? Links Repo: https://github.com/SingularityAI-Dev/logic-md LangGraph adapter: https://github.com/SingularityAI-Dev/logic-md/tree/main/adapters/langgraph Spec: https://github.com/SingularityAI-Dev/logic-md/blob/main/docs/SPEC.md Happy to pair with anyone who wants to push the adapter forward, or take feedback issues on the repo. 1 post - 1 participant Read full topic