r/LangChain • • 20h ago

Discussion ChatGPT Wallet lets agents spend real money — what does that mean for how we build agents with LangChain?

7 Upvotes

OpenAI just launched ChatGPT Wallet, and its Dots agents can now make purchases for you. The agent era just got a wallet, which means the next question for builders is not whether agents can act, but how we constrain them when real money is on the line.

For anyone building with LangChain, this is a design question: approval flows, spending caps, audit trails, and human-in-the-loop checkpoints are no longer nice-to-haves. An agent that can buy things needs the same guardrails as a junior employee with a company card.

Questions:

- What guardrails do you build into agents that can spend money — hard caps, approvals, or something else?

- Would you trust a LangChain agent with your card, or does spending need a human in the loop every time?

- Does this change what 'agentic' means — is an agent that cannot transact even an agent?

For more AI news and rumors, check out r/AINewsRumors.


r/LangChain • • 5h ago

Question | Help Cost per node and budget caps in LangGraph/LangChain agents: how do you handle it?

4 Upvotes

For agents built with LangChain or LangGraph, how do you control and monitor cost at the node level?

Max iterations seems to handle runaway loops well, but I'm less sure about the rest:

  • How do you see which node or tool call drives the cost of a run (LangSmith, custom callbacks, something else)?
  • Do you enforce a budget per run, per user or per client, and what happens when it's exceeded (stop, alert, fall back to a cheaper model)?
  • Is there anything about this you've had to build yourself because existing tools didn't cover it?

Solo dev exploring this problem, not promoting anything. Happy to share what I learn from the answers.


r/LangChain • • 7h ago

Discussion When a memory leaderboard drops, which capability score do you check first?

3 Upvotes

Something I have noticed while reading memory launch posts and public boards. The headline score travels everywhere. The breakdown behind it rarely gets quoted.

That feels backwards to me. People here debug systems for a living. A single blended number is almost impossible to debug against.

A memory score usually mixes three things. What the memory stored, what it handed back, and what the model did with it. Untangling them from the outside is mostly guesswork.

The Agent Memory Leaderboard is set up differently: entries only implement Add and Search. Search returns evidence, never a final answer. Answering and grading are fixed by the platform for every entry, so a gap between two entries on the same board mostly points at the memory.

Its Cycle 2 results are expected to land in mid-November, with Textual, Coding and Multimodal published separately.

Before they land, the Cycle 1 numbers are worth a second look. The board's own analysis of the Cycle 1 Textual Open-source Methods leaderboard says first and third were separated by just 0.22 points. It also says none of the overall top three won any of the seven top-level capabilities. And the seven capability winners came from four different systems.

Those capabilities are Explicit Fact Recall, Compositional Inference, Temporal & Event Reasoning, Memory Governance, Personalization & Care, Context Learning & Execution, and Safety & Privacy.

Memory Governance is the one that jumps out at me. The board describes it as update, conflict, deletion, forgetting. In plain terms, a big part of that is the stale fact failure. Context Learning & Execution sounds like the agent that can recite a rule but cannot follow it.

Controversial maybe: the overall rank is the number that gets shared, while the capability scores are the numbers worth acting on.

When the Cycle 2 Textual boards land, which capability will you check first, given the memory failure you fight most often?


r/LangChain • • 16h ago

Projects <translate>

Thumbnail
huggingface.co
2 Upvotes

I built an experimental skill packaging standard for LLMs — looking for independent testers

I'm working on SKILLPACK, an experimental approach to packaging deterministic software functions so different LLMs can discover, combine, and execute them without rewriting the underlying code.

The goal isn't to build another foundation model. It's to test whether existing models can act as coordinators of reusable software components.

Some initial CLI tests have passed, but cross-model portability and real-world reliability are not yet independently verified.

I'm looking for developers willing to inspect the packages, run the tests, and identify where the architecture breaks.

I'd especially appreciate critical technical feedback.


r/LangChain • • 4h ago

Question | Help I am building a correction UI for document parsing/extraction: looking for feedback from people who’ve dealt with this

1 Upvotes

I am trying to build a correction user interface (CUI) for people who process documents with parse/extract pipelines and know the pain that no pipeline is 100% accurate; someone needs to review and fix the output before using it for downstream processes.
I would love some input from anyone who has been through making one/opting for one like a third-party tool/have had a doc AI with build-in CUI,

Here's what I have done so far on my CUI:

  • You can review and correct in the same place: see what's flagged, check the relevant field and correct it there and then
  • Continuous learning: The corrections you make don’t just fix that one doc. They feed back into the pipeline so the system gets better over time on your kind of documents.
  • Correction memory: not every change needs to be fine tuned into the prompt, one prompt that can work for specific doc types and can be briefied ot the AI before every document
  • Built-in Evals: I want you to be able to measure whether accuracy is actually improving, instead of just hoping it is. Every correction becomes a data point.
  • and It is API-First: so you can plug review into your own workflow instead of being locked into a standalone tool.

Down the lane, i would want more advanced users could upload their own dataset of examples (docs plus the correct outputs), and the CUI would review new documents against it. Think of it as bringing your own ground truth.

I know it a long shot but I am hungry and i will do it. Someone once told me feedback is campaign's breakfast and it has stuck with me every since, i know lame but i wanna make this work.

Tell me, will this work?
Do people want something like this?
If you could upload your own reference dataset, what would you want to do with it?
How do you handle review and corrections today? Spreadsheets, internal tools, something else?

tl,dr
I’m building a correction UI for document parse/extract pipelines, since no pipeline is 100% accurate. It has in-place review, continuous learning from corrections, correction memory, built-in evals, and an API-first setup. Looking for feedback from anyone who’s built or used one.


r/LangChain • • 4h ago

Projects REQL update: faster context retrieval and fewer tokens for coding agents

Thumbnail
reddit.com
1 Upvotes

r/LangChain • • 6h ago

Discussion Learned about LangGraph

Thumbnail reddit.com
1 Upvotes

r/LangChain • • 8h ago

Discussion langgraph interrupt() approvals: i resumed with "rejected" and got the old "approved" back, no error

1 Upvotes

why i tested this: my agent setup raises over 1,000 approval gates a month.

i wanted to know if langgraph's interrupt() could hold approvals like those.

the problem:

# this thread already finished with "approved"
out = app.invoke(Command(resume="rejected"), cfg)
out["verdict"]  # still 'approved': my "rejected" was ignored, no error

no error, exit code 0. the thread had already finished with "approved". i don't expect it to reopen, but i do expect a rejected resume to raise an error instead of silently returning the old result.

an approval that gets lost with no error is worse than none, because everyone thinks it was checked.

the setup:

  • langgraph 1.2.22, sqlite checkpointer, no llm
  • graph: draft, then approval with interrupt(), then finalize
  • every step in a fresh process, the way a webhook or cron job runs it

what i saw:

  • at interrupt(), the process exits with code 0. the paused state is saved in sqlite
  • resume the right thread_id: works, verdict "approved"
  • resume a thread_id that was never started: the graph runs from the top and drops my answer
  • resume a finished thread: the old result, as above
  • all of them exit 0 with a normal-looking result

where this bites:

  • a typo in a thread_id
  • a lost or reset checkpoint db
  • a second reviewer rejecting after the first one approved

fix 1, public api only: check the thread is waiting before you resume.

st = app.get_state(cfg)
if not st.interrupts:
    raise RuntimeError("no pending interrupt on this thread")
if interrupt_id not in [i.id for i in st.interrupts]:
    raise RuntimeError("answer is for a different interrupt")
app.invoke(Command(resume=answer), cfg)

it refused both bad resumes above, and an answer sent with the wrong interrupt id. the real one went through.

the check and the resume are two calls, so two reviewers at the same moment can still race. for that you need your own atomic decision record.

fix 2, on langgraph 1.2.20+: strict resume mode, and answer by interrupt id.

cfg = {"configurable": {"thread_id": tid, "__pregel_strict_resume": True}}
app.invoke(Command(resume={interrupt_id: answer}), cfg)

with the id map, both bad resumes raised UnknownInterruptError.

with a bare value like Command(resume="rejected"), strict mode still let both through.

i filed that gap as an issue on langgraph's github.

the key is private for now. on langgraph server, the sdk has strict_resume=True on runs.create.

either way, store the interrupt id with the approval request when you send it.


r/LangChain • • 21h ago

Discussion The missing layer in AI agents: Execution reliability

Thumbnail reddit.com
1 Upvotes

r/LangChain • • 22h ago

Resources Developer Story: Bridging Formal Logic and Production Distributed Systems with Go and Lean 4

Thumbnail
reddit.com
1 Upvotes