Technical notes on how AshnaAI is built: Ashna-X1, agents, desktop connectors, voice, retrieval, and human approval.
AshnaAI’s agent builder writes a structured spec, not a free-text prompt dump. Tools are attached by internal IDs. Permissions that need OAuth or extra user data are requested in schema instead of being invented by the model.
AshnaAI controls the user’s own browser through an extension or desktop broker. It is not a hosted RPA farm. Actions are a closed list, every run needs an idempotency key, and secrets go to requestUserInput instead of the page.
AshnaAI can place and receive live calls through LiveKit telephony plus Twilio or Telnyx numbers. Inbound routing attaches a SIP trunk or voice webhook. Numbers are filtered for voice capability before purchase.
AshnaAI grounds answers in files the user already uploaded. Embeddings are queued in the background, linked to the chat before ingestion starts, and can be restarted if they go stale. The product retrieves from those files; it does not train a new model on them.
AshnaAI stops an agent before irreversible work by using requestUserInput and review gates. The input tool has four kinds: question, choice, file, and acknowledgement. Tally writes use the same idea as Need-review instead of silent creates.
