Sanad in your terminal and VS Code
Two coding clients bring Sanad into the repository, with account-based login, model selection, and approval before file changes or terminal commands.
Work where the code lives
Sanad now has a terminal client and a VS Code extension. Both connect through a Sanad account and bring the model into the working repository, where it can help with questions, planning, changes, debugging, and review.
The terminal client supports an interactive session as well as a focused one-shot request. The editor extension keeps the conversation alongside the code and starts its bundled local runtime automatically. Developers can choose the environment that fits the task without configuring a separate model provider.
Sign in through the browser
Login starts from the client and continues with a device confirmation in the browser. The client receives access to Sanad after that confirmation; upstream provider credentials do not need to be copied into the repository or local client settings.
Both clients use the Sanad model catalog. Sanad 0.1 is the default research-preview choice, with GLM 5.2 also available in this release. The selected model travels through the same account-based gateway in either environment.
Keep proposed work inspectable
File edits and terminal commands have approval boundaries by default. The developer can inspect the proposed change or command before allowing it to affect the workspace. Those decisions belong in the coding workflow, where the repository context is visible.
The clients also support follow-up conversation, so a developer can refine a request without starting a new exchange for every question. The goal of this release is a usable loop: understand the task, propose work, inspect it, and continue from the result.