Skip to content

Commit cefa14a

Browse files
Update README.md
1 parent a9d99ff commit cefa14a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ print(answer)
6969
# Why LitAI for agents?
7070
Agent frameworks are great for demos - but they’re hard to learn, full of custom syntax, and often unpredictable. They get you up and running fast with built-in agents, tools, and flows, but that speed comes at a cost: deep abstractions, hidden logic, and behavior you can’t easily debug. Even simple things like tool calls or prompt formatting get rewritten behind the scenes. Most teams eventually hit a wall and rebuild everything in plain Python just to make it work.
7171

72-
LitAI gives you that path from the start. There’s nothing new to learn - just write Python like you already know. You get the same building blocks you’d end up building yourself: model calls, retries, fallbacks, tool use, memory, streaming - all in clean, testable code. You control every prompt. Use `.chat()`, `.if_()`, or `.classify()` when the model should help. No wrappers. No YAML. No surprises. Just code that works the way you expect.
72+
LitAI gives you that path from the start. There’s nothing new to learn - just write a normal Python program like you already know and sprinkle in `.chat()`, `.if_()`, or `.classify()` as needed to make the program smart and agentic. With LitAI you get the same building blocks you’d end up building yourself: model calls, retries, fallbacks, tool use, memory, streaming - all in clean, testable code. You control every prompt. No wrappers. No YAML. No surprises. Just code that works the way you expect.
7373

7474
[Full comparison](https://lightning.ai/docs/litai/home/why-litai#comparisons)
7575

0 commit comments

Comments
 (0)