Chat is great, but canvas ux is better for working with documents
@hwchase17
-
Sick Canvas and Agent Experience Innovation
By
–
sick canvas + agent experience!!! https://t.co/HMmaj7amed
— Harrison Chase (@hwchase17) 19 mars 2025sick canvas + agent experience!!!
-
LangChain Customer Story: Rexera Implementation Success
By
–
heres a good customer story on trying out both https://
blog.langchain.dev/customers-rexe
ra/
… -
LangGraph Studio Enables Multi-Agent Distributed Systems Visualization
By
–
Multi agent systems with distributed subagents LangGraph Studio now supports visualizing and debugging these
-
Debugging Prompting Issues: Technical Solution Discussion
By
–
Probably a prompting issue. Ooc – can you say more about the use case? I can maybe hack something together
-
LangGraph Swarm: Multi-Agent Architecture with Handoff
By
–
I would look into langgraph swarm. Have one agent that is in change of getting the info, then hands off to another one that does the task:
-
LangGraph vs CrewAI: Low-Level Control and High-Level Frameworks
By
–
Langgraph is much lower level and more controllable. Crewai is higher level and off the shelf. We have some prebuilt packages that are built on top of langgraph that are similar to crew, like langgraph supervisor:
-
Canvas UX Becomes Standard for LLM Document Interaction
By
–
Canvas ux is becoming the standard for interacting with LLMs on documents Want to implement yourself? Check out open canvas! https://
github.com/langchain-ai/o
pen-canvas
… -
Low Code Agent Builder Debate and Criticism
By
–
And you were trying to argue for a low code agent builder??
-
No-Code Subgraph State Management with Message Lists
By
–
yes definitely. this is top of mind actually to do this in a no-code way, this would rely on some assumptions about the subgraph states. i think generally youd assume that their state has a list of messages. fine assumption?