Ready to help?
Looks at your AI service setup, configuration and the capabilities available to Vakyartha.
Meet Vakyartha Doctor
Let’s see what
needs attention.
A little check-up for your AI helper.
Find what’s ready, what needs a hand, and what to do next.
01 / First, take a look
A useful place
to start.
Perhaps voice has gone quiet. A connected chat cannot reach its working folder. Or something feels wrong after an update. Doctor checks the installation and gathers the problems into one report.
Ready to listen?
Checks enabled voice settings and the readiness of any local speech engines you have configured.
Work in the right place?
Checks saved-work storage and whether connected chats can still reach their assigned folders.
Installation in order?
Checks installation layout and version consistency. The command also reports managed services that exited with an error.
You get the check that failed and the reason it reported. The full report is available on your own installation.
02 / Make sense of it
From “something’s wrong”
to a next step.
A helpful diagnosis gives you somewhere to go. Some problems need a choice only you can make.
Voice has no model selected
Choose the model you want to use in Voice settings. Doctor can identify the missing choice.
A chat’s folder has moved
Point the connection to the correct workspace in Admin. Doctor leaves that decision to you.
An AI service needs a key
Add your own credential in Settings. Your account and access stay yours to choose.
Illustrative situations, written in everyday language. Your report shows the checks and details from your installation.
03 / A careful repair
A known fix.
Then another look.
When you ask Doctor to repair, it acts on the problems with a supported fix. It tells you what it attempted, then checks the installation again.
Anything that still needs your decision stays visible. A failed repair is reported as a failure.
What can it fix today?
An installation version mismatch can trigger a reinstall. Retired plugins have a cleanup path. Pending channel requests past their configured expiry can be denied, with the reason kept visible.
Repair can change your installation or channel state. Begin with the check-up and read the findings before asking for a repair.
When you need a hand
Your check-up
is close by.
On your running installation, the admin Operations Center brings Doctor’s core health report together with service, delivery and incident information.
A passing report means these checks passed at that moment. An external service or a later request can still encounter a problem.
Run a check-up from the terminal
In the working folder you use with Vakyartha, run:
vak doctorThe terminal’s conversation interface also offers /doctor.
Ask for a supported repair
After reviewing the diagnosis, run:
vak doctor --repairRead the fresh report afterwards. Problems without a known mechanical fix need your attention.
Look inside Doctor
Doctor is part of Vakyartha’s open-source runtime. You can inspect both the shared checks and the repair decisions.
Read the health checks ↗Read the repair logic ↗