2.9.26
Released 2 Nov 2026
AlphaWeft is a Windows 10/11 agent for dApp front ends on local chains and test networks. It edits your files, runs your own commands and shows each result in the chat. Version 2.9.26 is current.
src4 foldersbalance-abi.jsonloadedbalanceOf src3 matchessrc/Balance.jssavedsrc/index.html+4 linesyour test commandexit 0Released 2 Nov 2026
What the download button gives
A single .exe, also published
Interface languages of the app
Compare before you install
Shown when a new version is ready
Web3 development means building the front end, the smart contracts and the tooling between them. AlphaWeft works on the front-end side, inside your own project folder, where it maps files, reads the ABI, edits components and runs your build and test commands. Each result is a card. Version 2.9.26 shows the command output or the file diff when you expand it.
Open your dApp folder as the working folder and ask the agent to map it. list_dir shows the folders, glob finds the TypeScript and ABI files, and grep lists every place that calls a contract function; each result appears as a card in the chat. Nothing changes yet. Why do people drop off web3 apps? Often a transaction sits in pending and the screen never says so, which is why you note those components first. Read the cards, then pick 1 component to open next.
list_dir src → 4 folders
glob src/**/*.tsx → 7 matches
grep balanceOf → 3 matchesAsk for a connect-wallet button that shows 5 states: not connected, waiting for the wallet, connected, wrong network and rejected. write_file creates the component, edit_file adds it to the page, and Ask first pauses before each change so you can read the diff and accept or reject it. A button like this never needs a private key, because the user's own wallet signs. Shell then builds it. Run your build command, read the exit code on the card and try the screen on a test network.
write_file src/Connect.tsx → saved
edit_file src/App.tsx → +4 lines
Shell your build command → exit 0Point the agent at balance-abi.json. read_file loads the ABI, grep confirms that balanceOf is a view function, and write_file saves a short script that reads the balance of a throwaway test account through the JSON-RPC connection of your local chain. Shell runs it with your own command, and the card shows the real output and exit code. A beginner question about an ERC-721 contract, such as which function returns the owner of a token, gets the same treatment, because the ABI lists every function. Compare the output with your own node before you rely on it.
Ask the agent to run your build command. Shell returns the real exit code, here 1, and the expanded card shows the full error text. read_file opens the file named in the error, edit_file proposes a fix as a diff, and in Ask first mode you accept or reject it before anything is saved. Then it reruns. A passing build only shows that the code compiles, so run your test command as well and read its output before you move on to the next screen.
A chat assistant writes text. AlphaWeft version 2.9.26 for Windows 10 and 11 runs the tools itself, and every action appears as a card with its real result.
| Typical chat assistant | AlphaWeft | |
|---|---|---|
| File changes | Gives code for you to copy | Edits the file and shows a diff |
| Terminal | Describes commands to type | Runs your command, reports the exit code |
| Approval | Nothing to approve | Auto-run, Ask first or Plan only |
| Documentation | Answers from what it already knows | Reads pages with web_search and http_get |
Beginners learning dapp development get the most from visible steps. Start small. Each tool call is a card, so you can read the command, the file diff and the exit code for yourself instead of guessing, and the 5 transaction states give you a checklist for every screen you build.
A web3 developer with a working dApp can hand repetitive front-end work to the agent. Tests are one example. The agent writes them with edit_file, runs your test command and shows the exit code, and in Ask first mode you accept the diff only when it matches how you would have written it.
People planning a transition into blockchain developer roles can practise on a small project of their own. Build one screen. Read an ABI, call a view function on a test network, then write down how to run the project so that a stranger could follow it after only 1 read.
It is building the front end, the smart contracts and the tooling between them for apps that run on a blockchain. The contracts on EVM chains are usually written in Solidity. AlphaWeft handles the front end. It works in your project folder, on a local chain or a test network, and you review each change.
Yes, uideveloperweb.com is the official AlphaWeft website. The setup program is the original build. Verify it first. The installer is not code-signed yet, so compare its SHA-256 checksum with the published manifest before you run it, and use the Send feedback button inside the app to reach support.
Yes, through tools such as read_file and grep, and the file tools work in the working folder you choose for the chat. With a cloud model the text of those files goes to the provider as part of the prompt. With a local model nothing leaves your PC. Choose with that in mind.
It is building a front end that talks to smart contracts through a connection to a blockchain node. The page reads contract data through a JSON-RPC connection, and the user's own wallet signs every transaction that changes data. Keys stay in the wallet. Test the whole flow on a local chain before you move to a test network.
A checksum is a fingerprint of the file. In Windows, run certutil -hashfile with the path of the downloaded file and SHA256, then compare the result with the value in the published manifest. A mismatch means stop. The installer is not code-signed yet, so accept a SmartScreen warning only after the two values match.
Yes. AlphaWeft accepts a model running on your own PC, a cloud AI provider or the built-in model. With a local model nothing leaves the machine. The Test button checks an endpoint and shows its response time and its context window, so you know what you are connecting to.
A local chain or a test network, with throwaway accounts. Test coins have no value. They exist for this kind of testing. Never put a private key or seed phrase into code, files, chat or the repository, and get an independent security review before a contract holds anything of real value.
Version 2.9.26 is a download of about 34 MB for Windows 10 and 11. No account is needed. Pick a model, point AlphaWeft at a dApp folder on a local chain or test network, and review the first diff yourself.
Download AlphaWeft for Windows ↗Every page of this website is available in 20 languages.
What the agent does for dApp projects ↗ Cloud, local and built-in models ↗ Step-by-step dApp workflows ↗ Download and verify the installer ↗ Questions and answers ↗ Privacy of the site and the app ↗