Skip to main content
An agent is the hosted unit behind a stable URL - what an agent folder becomes when you deploy it. The link between your local folder and its agent is the karta git remote that karta deploy wires on first run: deploys are pushes to it, and commands like karta open infer the agent from it.

​
Deploy

karta deploy               # ship the agent in this folder
karta deploy support-bot   # ... or name it explicitly
karta deploy ships the current agent. On first run it provisions the hosted agent, wires the karta git remote, and prints the URL; thereafter a git repo pushes to that remote and a plain folder uploads. git push karta main is the transparent equivalent for a git repo: 
git push karta main
See Releases & rollback for the deploy flow in depth, including plain folders and CI.

​
Inspect

karta status                       # agents in this repo + their deploy status
karta agent list                   # all active agents in your org
karta agent show support-bot       # header + recent releases
CommandPurpose
statusAgents in the current repo joined to their deploy status.
agent listList your active agents.
agent show [slug]Agent header plus recent releases (the agent in this folder if no slug).

​
Roll back

karta rollback support-bot --to v3
Rollback flips the active release pointer back - instant, and the agent URL is unaffected. In-flight sessions finish on the release they started on.

​
Logs

karta logs support-bot --tail                     # follow via SSE
karta logs support-bot --since 2026-06-01T00:00:00Z

​
Open

karta open             # the hosted chat page (what customers embed)
karta open console     # the agent page in the dashboard
Run it inside the agent folder and the karta remote identifies the agent; elsewhere, pass -p <slug> or set KARTA_AGENT.

​
Where sessions fit

Local chat is karta dev: it runs your agent behind the consumer session API on your machine, with hot reload and a REPL - see the CLI overview. In production, sessions are driven through the session API by your frontend or the chat widget; the hosted chat page (karta open) is the quickest way to talk to a live deploy.
The retired Python karta kept a local agent registry (karta agent add/list/remove) and local session verbs (karta session …). Neither has a replacement because neither is needed: the folder plus its karta git remote replaces the registry, and karta dev replaces local session juggling.