Capabilities

6 modules online

What already makes Apsara useful today

The value is not speculative. These are the real behaviors that make the current CLI and backend feel more trustworthy than a generic AI tab.

01

workspace.init

Project-local init

Apsara starts inside the repo, keeps config where the work lives, and avoids the disconnected AI chat problem.

statuslocal
02

tools.scope

Workspace-scoped tools

Search, reads, writes, and line replacement stay bounded to the allowed root instead of wandering across the machine.

statusbounded
03

review.diff

Diff-first approvals

Meaningful changes stop at a review gate so the developer keeps the final say before edits apply.

statusrequired
04

trace.details

Hidden internals on demand

Tool activity stays quiet by default, while /details gives power users the exact work trail when they want it.

statuson demand
05

events.persist

Durable backend spine

FastAPI, Postgres persistence, usage tracking, and SSE streaming give the agent loop a real foundation.

statusdurable
06

session.resume

Persistent sessions

Conversation history and usage events stay durable so the workflow remains accountable across runs.

statusstateful