You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ print(answer)
69
69
# Why LitAI for agents?
70
70
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.
71
71
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.
0 commit comments