ElizaOS for Windows is a free, open-source framework for building AI agents that handle Web3 tasks. It is aimed at developers and technically confident users who want an agent that can chat, remember context, run automations and, when configured, take wallet actions on their behalf. Released under the MIT license and written mainly in JavaScript and TypeScript, it is published on GitHub, so you can read the code before you run it.
Be aware that the current release is a beta: the latest version is v2.0.11-beta.7, so expect rough edges and interfaces that may change. Because its wallet features touch real assets, careful setup and verification matter more here than with a typical chat app. The sections below cover what the program does, how to install it safely, how to start using it and where it fits among similar tools.
What Is an AI Agent Framework?
An AI agent framework is a set of building blocks for software that can hold a conversation, keep track of what it has learned and take actions on your behalf. Instead of a single chat window, an agent is usually connected to tools such as a calendar, a messaging app, a browser or a blockchain wallet. The framework supplies the glue: memory, request routing and the connections to those tools.
ElizaOS follows that pattern. Its Web3 focus means many of its tools are built around blockchain activity, and its wallet operations are designed to run with approval boundaries. Because the project is open source under the MIT license, developers can study how each piece works, change it or build their own agent on top.
Understanding these layers helps you decide how much autonomy to grant. A chat-only agent can make mistakes in words; an agent with wallet access can make mistakes with money. That difference is why the rest of this page pays close attention to approvals and key handling.
Who Is ElizaOS Built For?
ElizaOS suits three kinds of readers. Developers building Web3 applications can use it as a starting point for an agent that talks to users and interacts with smart contracts. Power users who already script their workflows may appreciate the automation and device bridges. Curious readers who want to see how an autonomous assistant behaves can explore it on a test machine without real funds.
It is less suited to people who want a polished consumer app with one-click setup. The current release is a beta, and the project assumes some comfort with configuration and with JavaScript tooling. Teams evaluating it for business use should review the code and the license terms before adopting it.
A practical way to start is to pick one narrow workflow, such as a scheduled reminder or a read-only query, and test it thoroughly before granting wider permissions. Expanding gradually makes it much easier to notice when an agent behaves in an unexpected way.
Understanding Approval Boundaries in Wallet Actions
An approval boundary is a checkpoint between what an agent wants to do and what actually happens. When an agent prepares a transaction, the boundary holds it until a person reviews the details and confirms. The idea is simple: the agent can propose, but a human decides.
This matters because automated systems can misread instructions, follow misleading content or act on outdated information. A boundary gives you a chance to catch a wrong recipient, an unexpected amount or an unfamiliar contract before funds move. It does not replace judgment; it places your judgment at the moment it matters most.
When you evaluate any agent with wallet features, look for clear prompts, readable transaction summaries and a simple way to reject an action. Also check which network a transaction targets. Solana and EVM-compatible networks use different address formats and fee models, so confirm the chain before you approve anything.
Key features
Chat, Voice, Memory and Knowledge Workflows
Messaging and Workspace Connectors
Personal Assistant Tools
Browser and Desktop Automation
Native Device Bridges
Non-Custodial EVM and Solana Wallet Operations
Scheduled Workflows and Coding Agents
Supported coins
The documentation specifically mentions Solana (SOL). The wallet features also cover EVM-compatible networks, which share conventions with Ethereum and many layer-2 chains. Confirm the network in every approval prompt, because the same address format can exist on several chains.
How to install ElizaOS on Windows
- 1
Download the installer from a trusted source
Download only from the official website or the project's GitHub Releases page at github.com/elizaOS/eliza. Avoid mirror sites, file-sharing links and downloads offered inside chat messages, since these may contain modified files. Choose the Windows build or installer listed for the version you want.
- 2
Verify the file before running it
Compare the file's SHA-256 checksum with the value published on the release page. In PowerShell, you can run Get-FileHash with the -Algorithm SHA256 option on the downloaded file and check that the output matches. If the project publishes a signature, verify it as well. Do not run a file whose checksum does not match.
- 3
Run the installer
Start the installer and follow the prompts. Pick an install folder you can find later and keep the default options unless you have a specific reason to change them. Windows may show a warning for software from an unfamiliar publisher; confirm it only after the checksum check has passed.
-
Start the program and review permissions
Open the program once to confirm it starts correctly. Before enabling connectors, device bridges or wallet features, look at what each one can access. Leave everything you do not need switched off, and keep your Windows updates and security software running.
How to use ElizaOS
ElizaOS is a framework rather than a single-purpose app, so your first session is about setting up a local agent and deciding what it may access. Start small, and widen permissions only after each workflow behaves the way you expect.
- Install the program using the steps above and open it once to confirm it starts.
- Choose the local runtime option so the agent runs on your own machine. Cloud sign-in is not required for this mode.
- Add your own model provider keys. Keep them private and do not paste them into shared chats, screenshots or support requests.
- Begin with a chat or document workflow to see how the agent responds to your instructions and whether its answers match your sources.
- Connect one messaging or workspace connector, then test a reminder or a simple scheduled task that you can easily check.
- Enable wallet features only if you need them. Use a test network or a small amount first, and read every approval prompt in full before confirming.
Keep a written list of each connector, device bridge and permission you turn on. If something looks wrong, that list lets you revoke access quickly.
Pros & cons
- Free to use and released under the MIT license, so you can use, study and modify the code
- Open source on GitHub, which lets you inspect the code before running it
- Broad feature set covering chat, memory, automation, connectors and device bridges
- Non-custodial Solana and EVM wallet operations with approval boundaries
- Local runtime option that does not require a cloud sign-in
- The current release is a beta (v2.0.11-beta.7), so behavior and interfaces may change between updates
- Wallet features carry financial risk and need careful setup and supervision
- Developer-oriented design; newcomers may find configuration technical
- A wide feature set means many settings to review before the program is safe to rely on
Is ElizaOS safe?
ElizaOS is open source under the MIT license, which lets you inspect the code, but that alone does not make every download safe. Download only from the official website or the project's GitHub Releases page at github.com/elizaOS/eliza, and avoid mirror sites or links shared in chats. Compare the file's SHA-256 checksum with the value published on the release page, and verify the signature if one is provided. Because the program can hold keys and prepare transactions, never enter a seed phrase on a third-party website or give it to anyone claiming to offer support. The release is a beta, so check the latest version on the official website before installing, and keep your antivirus and Windows updates active.
- Official source only. Download from github.com/elizaOS/eliza. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
ElizaOS sits in a different place from most tools in this catalog. Anchor helps developers write secure Solana programs, the on-chain contracts an agent may later call. Foundry gives smart contract developers forge, cast and anvil for testing and deployment, while Remix Desktop offers a Solidity IDE for writing and compiling contracts. Tenderly CLI focuses on debugging and monitoring contracts after deployment, and Alchemy, Infura and QuickNode provide RPC access to blockchain nodes.
ElizaOS differs because it is an agent framework. Its core job is to converse, remember and act through connectors and wallet operations rather than to write or test contracts. In practice, the tools complement each other: a developer might write and test a contract in Foundry, then use an agent built on ElizaOS to prepare calls to it under approval.
Specifications
- Price
- Free
- Type
- Open source
- License
- MIT
- Latest version
- v2.0.11-beta.7
- Last update
- 31 Oct 2026
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/elizaOS/eliza
Frequently asked questions
Yes, ElizaOS is free and released under the MIT license. The license allows you to use, copy, modify and distribute the code, subject to its notice terms. Being free does not mean there are no costs at all: any external model provider you connect may charge its own fees, so review that provider's pricing before you start.
It can be, if you take standard precautions. Get the file from the project's official source, compare its SHA-256 checksum with the published value, and keep your system updated. Because the program includes wallet features, grant only the permissions you need. The safety section above explains each step in more detail.
Start with the local runtime, connect your own model provider keys, and test a simple chat or document workflow. Add connectors and automation one at a time so you can see how each change affects behavior. Wallet features should come last, tested with small amounts or on a test network, and you should read every approval prompt before confirming.
ElizaOS describes its wallet operations as non-custodial, which means the design is meant to keep your keys under your control rather than handing them to a third party. Even so, keep your seed phrase offline and private. Never type it into a website or chat window that asks for it, because legitimate software has no reason to request your seed phrase that way.
The documentation specifically mentions Solana (SOL), and the wallet features cover both Solana and EVM-compatible networks. EVM networks share address and transaction conventions, so it is easy to send funds to the wrong chain. Always confirm the network name in the approval prompt before you approve any transaction.
No. The local runtime option runs the agent on your own machine, and Cloud sign-in is not required for that mode. You will still need your own provider keys for any model service you connect, and those accounts are separate from ElizaOS itself.
It is best treated as a beta. The latest version is v2.0.11-beta.7, so features may change between updates. It suits users who are comfortable reading release notes and reporting bugs, and developers who want to build on an open codebase.
Verdict
ElizaOS is a worthwhile option for developers and technically confident users who want an open-source agent framework covering Web3 tasks, messaging, automation and wallet operations. Its MIT license and public code make it easy to inspect, and the local runtime keeps you in control of your setup. Because the current release is a beta and the wallet features touch real funds, start with low-risk workflows, verify your download and grant permissions gradually. If you want a simple chat app with no configuration, a more polished consumer tool may suit you better.