README.md

LCE, LangGraph, and LangSmith are a powerful combination for building agents.
But the flexibility they allow can make it hard to get started.

This program shows some graph architectures taken from langchain/langgraph jupyter notebooks.

The DSL notation is non-standard, but serves two purpose:

1. shows a visual (text) representation of the graph
2. shows what functions need to be implemented (nodes and conditions)

This is equivalent to the builder code, but it's easier to understand. The equivalent builder code is generated from this text.

DSL syntax

1. START(StateClassNameGoesHere) => first_node

• "START" is a special node, include name of graph State class

2. node_name => next_node

• unconditional edge between nodes

3.  condition_1 => another_node
    condition_2 => yet_another_node
    => default_next_node
   

- conditional edges between nodes

Here's an example:

START(ModelCompare) => call_model

call_model => call_openai_model, call_anthropic_model

call_openai_model, call_anthropic_model => human_chooses

How to create an agent

1. Choose an initial langgraph architecture (left column)
2. Modify the architecture for your specific task (middle column, this is editable, the 'graph' tab shows the corresponding builder code)
3. Modify the generated functions to make the architecture functional (right column) -- these are currently read-only.

Why?

The end goal is really to simplify agent creation to make it easier for LLMs to build them.

Without getting too philosophical, for me, humans and agents are both tightly coupled and interchangeable. Think of it like a 'human-computer' being, with a varying percent of each.

So in theory, if my graph implementation is node and condition functions with known signatures, my agent building helper will be more helpful to me, because that's the level I understand.

Graph Specification DSL

The DSL translates directly into langgraph builder code. You see the DSL in the middle column, the 'Graph' tab in the right column shows the python code for the graph.

It's not that hard to just write the builder code, but there's two reasons you might find it useful:

1. You want to see your graph before you write the builder code.
2. You want to know what code you need to write for conditional edges.

Example

Here's a simple example that shows the syntax:

START(State) => agent_node

agent_node
  should_continue => tool_node
  => END

tool_node => agent_node

This tells me exactly what code I need to write:

1. START(State) -- this tells me I need a State class for my graph
2. agent_node, tool_node -- these are normal Nodes, functions that take state and return state updates
3. should_continue -- this is a boolean function that takes state and returns True if I should call tool_node

That's it. I can just look at the graph and know what code I need to write.

What does it look like in practice?

Here's a more complicated example -- a graph that takes user input, gives it to openai and anthropic, let's a human choose which result is better, and keeps a count until the user quits.

graph_spec = """

START(ModelCompare) => call_model

call_model => call_openai_model, call_anthropic_model

call_openai_model, call_anthropic_model => human_chooses

human_chooses => handle_human_request

handle_human_request
  wants_to_quit => END
  => call_model

"""

# make compiled graph in variable model_compare
graph_code = gen_graph("model_compare", graph_spec)
exec(graph_code)

model_compare.invoke({"human_request": "tell me a joke about turtles"})

This plus the 5 node functions, and the 1 conditional edge function, is the entire program.

The generated code (below) is not that complicated, but I can't see the graph and I can't make sense of what 'add_conditional_edges' is doing.

# BEGIN GENERATED CODE
model_compare = StateGraph(ModelCompare)
model_compare.add_node('call_model', call_model)
model_compare.add_node('call_openai_model', call_openai_model)
model_compare.add_node('call_anthropic_model', call_anthropic_model)
model_compare.add_node('human_chooses', human_chooses)
model_compare.add_node('handle_human_request', handle_human_request)
model_compare.add_edge(START, 'call_model')
model_compare.add_edge('call_model', 'call_openai_model')
model_compare.add_edge('call_model', 'call_anthropic_model')
model_compare.add_edge(['call_openai_model','call_anthropic_model'], 'human_chooses')
model_compare.add_edge('human_chooses', 'handle_human_request')
def after_handle_human_request(state: ModelCompare):
    if wants_to_quit(state):
        return 'END'
    return 'call_model'

handle_human_request_dict = {'END': END, 'call_model': 'call_model'}
model_compare.add_conditional_edges('handle_human_request', after_handle_human_request, handle_human_request_dict)

model_compare = model_compare.compile()
# END GENERATED CODE

Limitations

• No syntax checking, mistakes show up when executing generated code
• UI doesn't show any errors
• This is experimental, built with FastHTML
• A lot is not implemented, for now just collecting architectures to include