Raven 0.1.0
Raven 0.1.0 is the first public preview release of Raven, EverMind's memory-first, self-improving agent OS for terminal-native workflows.
This release line covers all Raven packages at version 0.1.0:
raven0.1.0: the Python CLI, agent runtime, memory integration, providers, channels, proactive engine, skills, plugins, sandbox, and developer workflow.raven-tui0.1.0: the native React/Ink terminal UI bundled into the release wheel as a self-contained build artifact.raven-whatsapp-bridge0.1.0: the WhatsApp bridge package used by Raven's messaging gateway/channel stack.
Highlights
- Memory-first agent runtime backed by EverOS for long-running sessions, reusable procedures, and persistent agent/user memory.
- Native command line product surface with one-shot CLI commands, onboarding, provider setup, diagnostics, session management, and gateway mode.
- Self-contained TUI packaging so installed wheels can run
raven tuiwithout requiring a source checkout or local npm build. - Proactive execution path through Sentinel, scheduling, nudge policy, and deferred decisions.
- Skill and plugin foundations for reusable, self-improving agent behavior.
- Multi-provider routing for OpenRouter, OpenAI, Anthropic, Gemini, DeepSeek, GitHub Copilot, OpenAI Codex OAuth, and OpenAI-compatible endpoints.
- Messaging/channel foundations for Telegram, Slack, Discord, WhatsApp, Matrix, Feishu, WeCom, MoChat, QQ, DingTalk, email, and Weixin extras.
- Public repository hygiene including CI, release build workflow, commit linting, pre-commit checks, security policy, contribution guide, and Apache-2.0 licensing.
Install
curl -fsSL http://raven.evermind.ai/install.sh | bashThen reload your shell and run:
raven onboardRelease Status
- Version:
0.1.0 - Tag:
v0.1.0 - Stability: public preview
- License: Apache-2.0
Notes
- Raven is not yet API stable. CLI surfaces, plugin contracts, and runtime internals may still change before v1.0.
- The GitHub release workflow builds wheel and sdist artifacts. PyPI publishing is not enabled in the workflow yet.
- Future releases should follow semantic versioning: patch releases for fixes, minor releases for new capabilities, and v1.0 once the public CLI and plugin contracts are stable.