Skip to main content

Nedura

AI agents. Your environment. Run Nedura in your own cloud tenant or on your servers, and connect it to approved AI model providers, chat tools, and business tools. Nedura is built and supported by ALINEDS. These docs cover setting it up, using it and extending it.

Install​

Installation

Nedura is installed and upgraded by your administrator with nedura-deploy (Linux, Windows Server, containers/Helm, Terraform). See Installation, or contact support@nedura.ai.

What is Nedura?​

It's not a coding copilot tethered to an IDE or a chatbot wrapper around a single API. It's an autonomous agent that gets more capable the longer it runs. It lives wherever you put it — a $5 VPS, a GPU cluster, or serverless infrastructure (Daytona, Modal) that costs nearly nothing when idle. Talk to it from Telegram while it works on a cloud VM you never SSH into yourself. It's not tied to your laptop.

🚀 InstallationInstalled and upgraded by your administrator with nedura-deploy
📖 Quickstart TutorialYour first conversation and key features to try
🗺️ Learning PathFind the right docs for your experience level
⚙️ ConfigurationConfig file, providers, models, and options
💬 Messaging GatewaySet up Telegram, Discord, Slack, WhatsApp, Teams, or more
🔧 Tools & Toolsets60+ built-in tools and how to configure them
🧠 Memory SystemPersistent memory that grows across sessions
📚 Skills SystemProcedural memory the agent creates and reuses
🔌 MCP IntegrationConnect to MCP servers, filter their tools, and extend Nedura safely
🧭 Use MCP with NeduraPractical MCP setup patterns, examples, and tutorials
🎙️ Voice ModeReal-time voice interaction in CLI, Telegram, Discord, and Discord VC
🗣️ Use Voice Mode with NeduraHands-on setup and usage patterns for Nedura voice workflows
🎭 Personality & SOUL.mdDefine Nedura's default voice with a global SOUL.md
📄 Context FilesProject context files that shape every conversation
🔒 SecurityCommand approval, authorization, container isolation
💡 Tips & Best PracticesQuick wins to get the most out of Nedura
🏗️ ArchitectureHow it works under the hood
❓ FAQ & TroubleshootingCommon questions and solutions

Key Features​

  • A closed learning loop — Agent-curated memory with periodic nudges, autonomous skill creation, skill self-improvement during use, FTS5 cross-session recall with LLM summarization, and Honcho dialectic user modeling
  • Runs anywhere, not just your laptop — 6 built-in terminal backends (local, Docker, SSH, Daytona, Modal, Vercel Sandbox) plus plugin backends such as Singularity. Daytona and Modal offer serverless persistence — your environment hibernates when idle, costing nearly nothing
  • Lives where you do — CLI, Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Mattermost, Email, SMS, DingTalk, Feishu, WeCom, Weixin, QQ Bot, Yuanbao, BlueBubbles, Home Assistant, Microsoft Teams, Google Chat, and more — 20+ platforms from one gateway
  • Built and supported by ALINEDS — Works with Nous Portal, OpenRouter, OpenAI, or any endpoint
  • Scheduled automations — Built-in cron with delivery to any platform
  • Delegates & parallelizes — Spawn isolated subagents for parallel workstreams. Programmatic Tool Calling via execute_code collapses multi-step pipelines into single inference calls
  • Open standard skills — Compatible with agentskills.io. Skills are portable, shareable, and community-contributed via the Skills Hub
  • Full web control — Search, extract, browse, vision, image generation, TTS — one subscription via Nous Portal bundles all of them
  • MCP support — Connect to any MCP server for extended tool capabilities
  • Research-ready — Batch processing, trajectory export, RL training with Atropos

For LLMs and coding agents​

Machine-readable entry points to this documentation:

  • /llms.txt — curated index of every doc page with short descriptions. ~17 KB, safe to load into an LLM context.
  • /llms-full.txt — every doc page concatenated into a single markdown file for one-shot ingestion. ~1.8 MB.

Both files also resolve at /docs/llms.txt and /docs/llms-full.txt. Generated fresh on every deploy.