Features · Web search
Grounded in today, not last year.
When web search is enabled for your account, the agent can look up current documentation mid-task. Results come back as titles, URLs and snippets, and the agent is instructed to cite what it used.
Verifying webhook signatures
docs.example.comCompute the HMAC over the raw body, then compare in constant time…
Webhook security checklist
security.example.orgValidate timestamps, rotate secrets, and reject unsigned payloads…
Interface illustration — sample results.
What it does
01
Server-backed
Search runs through your Devora API, so provider keys and quotas stay off the desktop.
02
Your provider
Tavily, Brave, Serper, Exa, Google CSE or a self-hosted SearXNG — with priority and fallback.
03
Sources included
Answers come with the links used, so you can check them before you trust them.
Details
What you can rely on.
The small print, written plainly — including the parts that depend on your account.
- The owner console tests each provider and encrypts keys at rest.
- Search is gated by readiness; when it is off, the agent works without it.
- Snippets are retrieved from the provider, not invented by the model.
Availability
Requires your team to enable a search provider. Availability depends on your account configuration.
Keep exploring.
Try Devora.
Install the desktop app, open your project, and start with a question about your own codebase.
Windows 10 & 11 · Local workspace · Reviewable edits