01 / Why it feels better
More bounded than chat. More legible than autopilot.
The system does real work, but it never asks the developer to stop caring about scope, review, or authorship.
raw chatunboundedapsararepo-bound
Local-first CLI · no Apsara account required
Your coding agent. Inside your repo. On your machine.
Install the CLI, bring a model API key, and start coding. Apsara keeps your repositories, sessions, checkpoints, and project memory local while you stay in control of every meaningful change.
$
pipx install apsara-agenticapsara runtime
agent.tsreview.ts
1
const agent = await apsara.inside("./repo");2
const plan = await agent.trace({3
intent: "refactor approval flow",4
guardrail: "human-review"5
});6
return plan.review();✓
Patch prepared · 2 files changed
Waiting for human approval before write
01Repo-bound
Project-local init and config stay with the codebase.
02Diff-first
Meaningful edits pause for human review before they land.
03Session-aware
The workflow keeps durable context instead of resetting every time.
Product View
Runtime / 01—04
See the agent loop as a product, not just a prompt box.
This is the part worth showing. Project-local startup, bounded tools, hidden internals on demand, and a review step before edits land all turn the agent loop into something developers can actually trust.
apsara session
scope / repodiff / readystate / safe
scroll trace04
02 / checkpoint
Approval gate
The developer reviews the diff before meaningful writes touch the repo.
● agent.event
status: "awaiting_review"
03 / checkpoint
Quiet internals
Tool chatter stays hidden until /details is explicitly opened.
● agent.event
status: "details_available"
04 / checkpoint
Legible progress
The workflow surfaces what changed, why it changed, and what still needs a decision.
● agent.event
status: "context_persisted"
Product tone
Calm enough to trust. Clear enough to inspect. Useful enough to keep using.
Human loop
Trust grows when every step has a boundary.
That means workspace scoping, review gates before writes, and internal activity that stays available without taking over the entire interface.
// Review stays in the critical path instead of getting bolted on after the fact.
Capabilities
6 modules online
What already makes Apsara useful today
The value is not speculative. These are the real local behaviors that make the CLI 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 local runtime
Typed run state, local journals, checkpoints, and verification keep the agent loop inspectable without a hosted Apsara backend.
statusdurable
06
session.resume
Persistent sessions
Conversation history and usage events stay on your machine so work remains durable without cloud synchronization.
statusstateful
How It Works
A workflow that mirrors how developers already work.
Bring your provider, initialize the repo, and start coding. No Apsara account or cloud workspace sits between you and your tools.
$one safe loop, end to end
Step 01
agent loopConnect your model provider
Run apsara login and save your OpenCode, OpenAI, Anthropic, Google, Groq, or other provider key locally.
$
apsara loginStep 02
agent loopInitialize your repository
Run apsara init inside the project so workspace boundaries, instructions, and local configuration live with the codebase.
$
apsara initStep 03
human gateStart the local agent
Run apsara chat, ask for meaningful work, and review or reject changes before they land.
$
apsara chatStart locally
One CLI. Your provider.Your code stays yours.
Install Apsara without creating an account, connect the model you already use, and keep the complete coding workflow on your machine.