Skip to content

Releases

Meevra Code 2.45.0

Choose a tag to compare

@MeevraCode MeevraCode released this 22 Nov 11:17

Meevra Code 2.45.0 - Public Preview

Meevra Code is an AI coding workspace for Windows. It works with the AI accounts you already have, keeps your work on your computer, and checks what its agents say they did. You open a project folder and describe what you want built, fixed or changed. A Lead agent plans and does the work with helper roles under your rules, and Meevra Code itself checks the result with real test runs before it calls anything done.

Download and install

  1. Download MeevraCode.exe below and run it. It installs Meevra Code on Windows 10 or Windows 11, 64-bit (x64).
  2. Read the license agreement and choose I Agree.
  3. Open Providers and connect at least one AI: an account you sign in to (Claude Code, ChatGPT or Grok Build), an API key, or a local model.

The preview installer is not code-signed yet, so Windows SmartScreen may show "Windows protected your PC". If you downloaded the installer from this page, choose More info, then Run anyway.

Already installed? You do not need this file. Meevra Code offers the update in Settings > Updates. An installed 2.44.2 takes this release as a small update (about 2 MB), and older versions take the full installer. Your projects, chats and settings are kept.

What's new in 2.45.0

  • An agent is shown your project's own code. With every request Meevra Code picks the parts of your project that match it and gives them to the agent. Three things were wrong there and are fixed. Files your .gitignore keeps out (build output, caches, data) were picked and could crowd out the code. A folder named app or update was skipped whole, so a project that keeps its code in app/ had none of it picked. And in JavaScript and TypeScript only function and class declarations were found: arrow functions, constants and methods are found now.
  • Any language. Python, Go, Rust, Java, Kotlin, C#, C and C++, Ruby, PHP, Swift, Scala, Dart, shell, Lua, Elixir and SQL files are now read for the names inside them (functions, classes, types), for that selection and for Brain's map of your project. It reads names only, on your computer: no model is used for it and nothing new leaves your computer.
  • Fewer tokens on some requests. A request whose words matched nothing in the project used to get a long list of unrelated files, and one very long file could be added whole to every request of a task. Both now stay within the same limit as every other request.
  • After the update each project is read through once more, in the background, so that the names are found in files that did not change.
  • Current API prices. "What the API would charge" in Quota > Where it went uses the public list prices of 22 November 2026, for 217 models.

The license agreement is still version 1.6, so you are not asked to accept it again.

What came in 2.44.2

  • Your connections are named as accounts and sign-ins. Meevra Code now says Claude account and ChatGPT account for the connection, and Sign in to Claude Code or Sign in to ChatGPT for the step that makes it, everywhere in the app: Settings > Providers, the model list, Quota, the welcome screen, the Disconnect and Sign out dialogs. Messages about a limit say "usage limit". Only the words changed: your connections, models and settings work as before.

What came in 2.44.1

  • The license agreement names the browser pane. Version 1.6 of the agreement adds the browser pane to the list of internet connections in its Privacy section: the websites you open in the pane, the pages an agent opens there when you ask it to, that the pane's sign-ins, cookies and site data stay on your computer, and that an agent working there is signed in where you signed in. Because the agreement changed, Meevra Code shows it once more at the next start and asks you to accept it.

Everything in Meevra Code

Work

  • Code. Describe a task once. A Lead plans, hands scoped work to helpers and integrates the result. The helper roles are Investigator (read only), Implementer (writes only inside the task's scope), Reviewer (read only), Diagnostician and Tester. A role's permissions are fixed: a prompt cannot give a read-only role the right to write.
  • Chat. A conversation with a model that has no access to your files and runs no commands.
  • Reply. Answer any message of a thread, with a quote, also while a task is running.
  • Approval levels. Every step asks before anything that changes something. Balanced lets everyday development run and still asks for network access, installs, screen control and changes outside the workspace. Full access runs every action without asking.
  • Checkpoints. Every step that changes files is saved, and you can rewind a session to any step.
  • A branch per session (optional). A Code session can work in its own Git worktree, so your checkout stays untouched until you merge. Nothing is forced and nothing is pushed.
  • Delivery. From a finished task to a pull request: Meevra Code pushes only the files the session's tasks changed, opens the pull request on GitHub, reads its checks and can send a failed check back to the agent. It asks you to confirm in its own window first. No model is used.
  • Race. Several models do the same task, each in its own copy of the project. Meevra Code shows measured facts for each one and a judge's opinion, with the model names shown only after it. You take one version or combine them file by file, and the tests run again.
  • Bots. Bots that tidy, summarise or digest your folders, with your approval.
  • Night shift. Queue a task for the night. It runs on plan quota that would otherwise be lost before the reset, never on a route that costs money.
  • Computer use. Agents can see the screen and use the apps you allow. It is off until you turn it on, the screen edges glow while it works, and Stop works at any moment.
  • Terminal. Run approved shell commands inside the app, on its own page or in a pane beside your work.
  • Browser pane. A browser with tabs beside your work. It keeps its sign-ins on your computer, and an agent can work in it when you ask.
  • Keep computer awake. A switch that keeps the computer from sleeping during a long task.

Checks that use no model

  • Proof it works. Before a task may end as done, Meevra Code runs your tests and your typecheck or build itself and shows the exact commands and their results.
  • Test truth. It checks whether the agent's new tests would fail without the change. A test that passes either way is marked "Doesn't check the change".
  • Claims checker. Every claim the agent makes at the end (tests passed, build OK, files changed, nothing left) is compared with Meevra Code's own records and shown as verified, not verified or contradicted.
  • Proof strength. In a temporary copy of your project Meevra Code makes one small break at a time in the changed lines and shows which breaks your tests noticed.
  • Error catcher. Errors from the commands, test runs and pages Meevra Code starts become cards mapped to your files, with Fix it.
  • Stuck detector. A task that goes in circles is paused early, with a plain explanation, before it burns your quota.
  • Promise. A running task shows how many turns and how much time tasks like it usually take, from your own record. A task that reaches twice its promise is held and asks you.
  • Reflexes. A finished task that was a set of commands can be saved and run again with no model at all.

See what is happening

  • Mission Control. Who works on what right now, the latest activity, and what waits for you.
  • Flow. Every project at work, drawn live: each agent, its model and speed, the file it works on and its tokens.
  • Activity. The audit trail of tasks, approvals, tests and provider events.
  • Quota. Plan limits and usage exactly as providers report them, a forecast, who used what, and Where it went: every model turn by model, effort, task and day, with what the API would charge for the same tokens.
  • Mobile. Pair your phone with a QR code and follow your tasks from it.
  • TV & second screen (experimental). Extend or mirror Meevra Code to a TV or a second screen.

Memory and knowledge

  • Brain. What Meevra Code remembers about your projects, chats and agents, stored on your computer. It learns from what really happened: a test command that ran and passed, a script that fails, what a finished task did. Agents get a small capsule of the memory that fits the task, as reference data and never as instructions.
  • Vault. Notes and reference text, encrypted on your computer, that you add to a chat or a task yourself.
  • Scout. A small, quick read-only helper that reads files for your agents, so the Lead's larger model does not spend its turns on reading.

Models and tools

  • Agents. A model, a reasoning effort and a prompt for each role. The model is Fixed, Preferred (your ordered list) or Auto. Each agent can have its own budget, and team presets can be saved, exported and imported.
  • Tools & MCP. The built-in tools and their rules, MCP servers, and a Marketplace of tools from the official MCP Registry.
  • Skills. Thirteen built-in skills for video, images, SVG, websites and model comparison, on from the first start. You can add your own or install more from GitHub. An agent reads a skill only when the task needs it.

Supported AI connections

Connection How you connect
Claude Code Sign in to Claude Code: Anthropic's own sign-in opens in its own window. Claude Code ships inside Meevra Code unmodified
ChatGPT Sign in to ChatGPT: OpenAI's own sign-in opens in your browser
Grok Build (xAI) xAI's own sign-in
Coding plans The plan's own key: Z.ai GLM Coding Plan, MiniMax M Plan, BytePlus ModelArk Coding Plan, StepFun Step Plan
Anthropic API, OpenAI API, OpenRouter, Xiaomi MiMo API key (...
Read more

Meevra Code 2.44.2

Choose a tag to compare

@MeevraCode MeevraCode released this 20 Nov 12:12

Meevra Code 2.44.2 - Public Preview

Meevra Code is an AI coding workspace for Windows. It works with the AI accounts you already have, keeps your work on your computer, and checks what its agents say they did. You open a project folder and describe what you want built, fixed or changed. A Lead agent plans and does the work with helper roles under your rules, and Meevra Code itself checks the result with real test runs before it calls anything done.

Download and install

  1. Download MeevraCode.exe below and run it. It installs Meevra Code on Windows 10 or Windows 11, 64-bit (x64).
  2. Read the license agreement and choose I Agree.
  3. Open Providers and connect at least one AI: an account you sign in to (Claude Code, ChatGPT or Grok Build), an API key, or a local model.

The preview installer is not code-signed yet, so Windows SmartScreen may show "Windows protected your PC". If you downloaded the installer from this page, choose More info, then Run anyway.

Already installed? You do not need this file. Meevra Code offers the update in Settings > Updates. An installed 2.44.1 takes this release as a small update (about 1.3 MB), and older versions take the full installer. Your projects, chats and settings are kept.

What's new in 2.44.2

  • Your connections are named as accounts and sign-ins. Meevra Code now says Claude account and ChatGPT account for the connection, and Sign in to Claude Code or Sign in to ChatGPT for the step that makes it, everywhere in the app: Settings > Providers, the model list, Quota, the welcome screen, the Disconnect and Sign out dialogs. Messages about a limit say "usage limit". Only the words changed: your connections, models and settings work as before.
  • Current API prices. "What the API would charge" in Quota > Where it went uses the public list prices of 20 November 2026, for 217 models.

Nothing else changed since 2.44.1. The license agreement is still version 1.6, so you are not asked to accept it again.

What came in 2.44.1

  • The license agreement names the browser pane. Version 1.6 of the agreement adds the browser pane to the list of internet connections in its Privacy section: the websites you open in the pane, the pages an agent opens there when you ask it to, that the pane's sign-ins, cookies and site data stay on your computer, and that an agent working there is signed in where you signed in. Because the agreement changed, Meevra Code shows it once more at the next start and asks you to accept it.

What came in 2.44.0

  • A terminal or a browser beside your work. Two buttons in the title bar open a pane next to the page you are on: Terminal (Ctrl+`) and Browser (Ctrl+Shift+B). Drag the pane's edge to make it wider or narrower.
  • The browser pane. Tabs, an address bar that also searches, back, forward and reload. The pane has its own session that stays on your computer, so a site you sign in to there stays signed in. Forget sign-ins and site data clears it.
  • The agent can work in the browser pane. Ask for it in a Code task, for example "open the preview in the browser pane and try the form". The agent gets its own Agent tab beside your tabs and opens pages, clicks, types, reads and takes screenshots there, while you watch. It works in the pane's session, so it is signed in where you signed in. Its approval request says so: "in your browser pane, where your sign-ins are".
  • Thirteen built-in skills. They ship with Meevra Code and are on from the first start: video prompting, video editing with ffmpeg, Remotion, image generation, image editing, image upscaling, text in images, logo design in SVG, SVG quality, website design, model comparison, and two that choose the right image or video tool. The agent sees one line for each skill and reads a skill only when the task needs it. You find them in Marketplace > Skills with a Built in mark, and each can be turned off.
  • Keep computer awake. A switch in the title bar's More menu keeps the computer from sleeping while a long task runs. It lasts until you turn it off or close the app.

Everything in Meevra Code

Work

  • Code. Describe a task once. A Lead plans, hands scoped work to helpers and integrates the result. The helper roles are Investigator (read only), Implementer (writes only inside the task's scope), Reviewer (read only), Diagnostician and Tester. A role's permissions are fixed: a prompt cannot give a read-only role the right to write.
  • Chat. A conversation with a model that has no access to your files and runs no commands.
  • Reply. Answer any message of a thread, with a quote, also while a task is running.
  • Approval levels. Every step asks before anything that changes something. Balanced lets everyday development run and still asks for network access, installs, screen control and changes outside the workspace. Full access runs every action without asking.
  • Checkpoints. Every step that changes files is saved, and you can rewind a session to any step.
  • A branch per session (optional). A Code session can work in its own Git worktree, so your checkout stays untouched until you merge. Nothing is forced and nothing is pushed.
  • Delivery. From a finished task to a pull request: Meevra Code pushes only the files the session's tasks changed, opens the pull request on GitHub, reads its checks and can send a failed check back to the agent. It asks you to confirm in its own window first. No model is used.
  • Race. Several models do the same task, each in its own copy of the project. Meevra Code shows measured facts for each one and a judge's opinion, with the model names shown only after it. You take one version or combine them file by file, and the tests run again.
  • Bots. Bots that tidy, summarise or digest your folders, with your approval.
  • Night shift. Queue a task for the night. It runs on plan quota that would otherwise be lost before the reset, never on a route that costs money.
  • Computer use. Agents can see the screen and use the apps you allow. It is off until you turn it on, the screen edges glow while it works, and Stop works at any moment.
  • Terminal. Run approved shell commands inside the app, on its own page or in a pane beside your work.
  • Browser pane. A browser with tabs beside your work. It keeps its sign-ins on your computer, and an agent can work in it when you ask.
  • Keep computer awake. A switch that keeps the computer from sleeping during a long task.

Checks that use no model

  • Proof it works. Before a task may end as done, Meevra Code runs your tests and your typecheck or build itself and shows the exact commands and their results.
  • Test truth. It checks whether the agent's new tests would fail without the change. A test that passes either way is marked "Doesn't check the change".
  • Claims checker. Every claim the agent makes at the end (tests passed, build OK, files changed, nothing left) is compared with Meevra Code's own records and shown as verified, not verified or contradicted.
  • Proof strength. In a temporary copy of your project Meevra Code makes one small break at a time in the changed lines and shows which breaks your tests noticed.
  • Error catcher. Errors from the commands, test runs and pages Meevra Code starts become cards mapped to your files, with Fix it.
  • Stuck detector. A task that goes in circles is paused early, with a plain explanation, before it burns your quota.
  • Promise. A running task shows how many turns and how much time tasks like it usually take, from your own record. A task that reaches twice its promise is held and asks you.
  • Reflexes. A finished task that was a set of commands can be saved and run again with no model at all.

See what is happening

  • Mission Control. Who works on what right now, the latest activity, and what waits for you.
  • Flow. Every project at work, drawn live: each agent, its model and speed, the file it works on and its tokens.
  • Activity. The audit trail of tasks, approvals, tests and provider events.
  • Quota. Plan limits and usage exactly as providers report them, a forecast, who used what, and Where it went: every model turn by model, effort, task and day, with what the API would charge for the same tokens.
  • Mobile. Pair your phone with a QR code and follow your tasks from it.
  • TV & second screen (experimental). Extend or mirror Meevra Code to a TV or a second screen.

Memory and knowledge

  • Brain. What Meevra Code remembers about your projects, chats and agents, stored on your computer. It learns from what really happened: a test command that ran and passed, a script that fails, what a finished task did. Agents get a small capsule of the memory that fits the task, as reference data and never as instructions.
  • Vault. Notes and reference text, encrypted on your computer, that you add to a chat or a task yourself.
  • Scout. A small, quick read-only helper that reads files for your agents, so the Lead's larger model does not spend its turns on reading.

Models and tools

  • Agents. A model, a reasoning effort and a prompt for each role. The model is Fixed, Preferred (your ordered list) or Auto. Each agent can have its own budget, and team presets can be saved, exported and imported.
  • Tools & MCP. The built-in tools and their rules, MCP servers, and a Marketplace of tools from the official MCP Registry.
  • Skills. Thirteen built-in skills for video, images, SVG, websites and model comparison, on from the first start. You can add your own or install more from GitHub. An agent reads a skill only when the task needs it.

Supported AI connections

Connection How you connect
Claude Code Sign in to Claude Code: Anthropic's own sign-in opens in its own window. Claude Code ships inside Meevra Code unmodified
ChatGPT *Si...
Read more

Meevra Code 2.44.1

Choose a tag to compare

@MeevraCode MeevraCode released this 19 Nov 17:41

Meevra Code 2.44.1 - Public Preview

Meevra Code is an AI coding workspace for Windows. It works with the AI accounts you already have, keeps your work on your computer, and checks what its agents say they did. You open a project folder and describe what you want built, fixed or changed. A Lead agent plans and does the work with helper roles under your rules, and Meevra Code itself checks the result with real test runs before it calls anything done.

Download and install

  1. Download MeevraCode.exe below and run it. It installs Meevra Code on Windows 10 or Windows 11, 64-bit (x64).
  2. Read the license agreement and choose I Agree.
  3. Open Providers and connect at least one AI: an account you sign in to (Claude Code, ChatGPT or Grok Build), an API key, or a local model.

The preview installer is not code-signed yet, so Windows SmartScreen may show "Windows protected your PC". If you downloaded the installer from this page, choose More info, then Run anyway.

Already installed? You do not need this file. Meevra Code offers the update in Settings > Updates. An installed 2.44.0 takes this release as a small update (about 0.5 MB), and older versions take the full installer. Your projects, chats and settings are kept.

What's new in 2.44.1

  • The license agreement names the browser pane. Version 1.6 of the agreement adds the browser pane to the list of internet connections in its Privacy section: the websites you open in the pane, the pages an agent opens there when you ask it to, that the pane's sign-ins, cookies and site data stay on your computer, and that an agent working there is signed in where you signed in. Because the agreement changed, Meevra Code shows it once more at the next start and asks you to accept it.
  • Current API prices. "What the API would charge" in Quota > Where it went uses the public list prices of 19 November 2026, for 217 models.

Nothing else changed since 2.44.0.

What came in 2.44.0

  • A terminal or a browser beside your work. Two buttons in the title bar open a pane next to the page you are on: Terminal (Ctrl+`) and Browser (Ctrl+Shift+B). Drag the pane's edge to make it wider or narrower.
  • The browser pane. Tabs, an address bar that also searches, back, forward and reload. The pane has its own session that stays on your computer, so a site you sign in to there stays signed in. Forget sign-ins and site data clears it.
  • The agent can work in the browser pane. Ask for it in a Code task, for example "open the preview in the browser pane and try the form". The agent gets its own Agent tab beside your tabs and opens pages, clicks, types, reads and takes screenshots there, while you watch. It works in the pane's session, so it is signed in where you signed in. Its approval request says so: "in your browser pane, where your sign-ins are".
  • Thirteen built-in skills. They ship with Meevra Code and are on from the first start: video prompting, video editing with ffmpeg, Remotion, image generation, image editing, image upscaling, text in images, logo design in SVG, SVG quality, website design, model comparison, and two that choose the right image or video tool. The agent sees one line for each skill and reads a skill only when the task needs it. You find them in Marketplace > Skills with a Built in mark, and each can be turned off.
  • Keep computer awake. A switch in the title bar's More menu keeps the computer from sleeping while a long task runs. It lasts until you turn it off or close the app.

What came in 2.42.3

  • A new Chat never starts on a model you removed. When you disconnect a connection in Providers, a new Chat no longer opens on a model of that connection. It uses the same model as Code until you choose one.
  • A Chat you already used keeps its model. Its history stays as it was. The model is shown as not available until you choose another one.

Everything in Meevra Code

Work

  • Code. Describe a task once. A Lead plans, hands scoped work to helpers and integrates the result. The helper roles are Investigator (read only), Implementer (writes only inside the task's scope), Reviewer (read only), Diagnostician and Tester. A role's permissions are fixed: a prompt cannot give a read-only role the right to write.
  • Chat. A conversation with a model that has no access to your files and runs no commands.
  • Reply. Answer any message of a thread, with a quote, also while a task is running.
  • Approval levels. Every step asks before anything that changes something. Balanced lets everyday development run and still asks for network access, installs, screen control and changes outside the workspace. Full access runs every action without asking.
  • Checkpoints. Every step that changes files is saved, and you can rewind a session to any step.
  • A branch per session (optional). A Code session can work in its own Git worktree, so your checkout stays untouched until you merge. Nothing is forced and nothing is pushed.
  • Delivery. From a finished task to a pull request: Meevra Code pushes only the files the session's tasks changed, opens the pull request on GitHub, reads its checks and can send a failed check back to the agent. It asks you to confirm in its own window first. No model is used.
  • Race. Several models do the same task, each in its own copy of the project. Meevra Code shows measured facts for each one and a judge's opinion, with the model names shown only after it. You take one version or combine them file by file, and the tests run again.
  • Bots. Bots that tidy, summarise or digest your folders, with your approval.
  • Night shift. Queue a task for the night. It runs on plan quota that would otherwise be lost before the reset, never on a route that costs money.
  • Computer use. Agents can see the screen and use the apps you allow. It is off until you turn it on, the screen edges glow while it works, and Stop works at any moment.
  • Terminal. Run approved shell commands inside the app, on its own page or in a pane beside your work.
  • Browser pane. A browser with tabs beside your work. It keeps its sign-ins on your computer, and an agent can work in it when you ask.
  • Keep computer awake. A switch that keeps the computer from sleeping during a long task.

Checks that use no model

  • Proof it works. Before a task may end as done, Meevra Code runs your tests and your typecheck or build itself and shows the exact commands and their results.
  • Test truth. It checks whether the agent's new tests would fail without the change. A test that passes either way is marked "Doesn't check the change".
  • Claims checker. Every claim the agent makes at the end (tests passed, build OK, files changed, nothing left) is compared with Meevra Code's own records and shown as verified, not verified or contradicted.
  • Proof strength. In a temporary copy of your project Meevra Code makes one small break at a time in the changed lines and shows which breaks your tests noticed.
  • Error catcher. Errors from the commands, test runs and pages Meevra Code starts become cards mapped to your files, with Fix it.
  • Stuck detector. A task that goes in circles is paused early, with a plain explanation, before it burns your quota.
  • Promise. A running task shows how many turns and how much time tasks like it usually take, from your own record. A task that reaches twice its promise is held and asks you.
  • Reflexes. A finished task that was a set of commands can be saved and run again with no model at all.

See what is happening

  • Mission Control. Who works on what right now, the latest activity, and what waits for you.
  • Flow. Every project at work, drawn live: each agent, its model and speed, the file it works on and its tokens.
  • Activity. The audit trail of tasks, approvals, tests and provider events.
  • Quota. Plan limits and usage exactly as providers report them, a forecast, who used what, and Where it went: every model turn by model, effort, task and day, with what the API would charge for the same tokens.
  • Mobile. Pair your phone with a QR code and follow your tasks from it.
  • TV & second screen (experimental). Extend or mirror Meevra Code to a TV or a second screen.

Memory and knowledge

  • Brain. What Meevra Code remembers about your projects, chats and agents, stored on your computer. It learns from what really happened: a test command that ran and passed, a script that fails, what a finished task did. Agents get a small capsule of the memory that fits the task, as reference data and never as instructions.
  • Vault. Notes and reference text, encrypted on your computer, that you add to a chat or a task yourself.
  • Scout. A small, quick read-only helper that reads files for your agents, so the Lead's larger model does not spend its turns on reading.

Models and tools

  • Agents. A model, a reasoning effort and a prompt for each role. The model is Fixed, Preferred (your ordered list) or Auto. Each agent can have its own budget, and team presets can be saved, exported and imported.
  • Tools & MCP. The built-in tools and their rules, MCP servers, and a Marketplace of tools from the official MCP Registry.
  • Skills. Thirteen built-in skills for video, images, SVG, websites and model comparison, on from the first start. You can add your own or install more from GitHub. An agent reads a skill only when the task needs it.

Supported AI connections

Connection How you connect
Claude Code Sign in to Claude Code: Anthropic's own sign-in opens in its own window. Claude Code ships inside Meevra Code unmodified
ChatGPT Sign in to ChatGPT: OpenAI's own sign-in opens in your browser
Grok Build (xAI) xAI's own sign-in
Coding plans The plan's own key: Z.ai GLM Coding Plan, MiniMax M Plan, BytePlus ModelArk Co...
Read more

Meevra Code 2.44.0

Choose a tag to compare

@MeevraCode MeevraCode released this 19 Nov 15:24

Meevra Code 2.44.0 - Public Preview

Meevra Code is an AI coding workspace for Windows. It works with the AI accounts you already have, keeps your work on your computer, and checks what its agents say they did. You open a project folder and describe what you want built, fixed or changed. A Lead agent plans and does the work with helper roles under your rules, and Meevra Code itself checks the result with real test runs before it calls anything done.

Download and install

  1. Download MeevraCode.exe below and run it. It installs Meevra Code on Windows 10 or Windows 11, 64-bit (x64).
  2. Read the license agreement and choose I Agree.
  3. Open Providers and connect at least one AI: an account you sign in to (Claude Code, ChatGPT or Grok Build), an API key, or a local model.

The preview installer is not code-signed yet, so Windows SmartScreen may show "Windows protected your PC". If you downloaded the installer from this page, choose More info, then Run anyway.

Already installed? You do not need this file. Meevra Code offers the update in Settings > Updates. An installed 2.42.3 takes this release as a small update (about 3 MB), and older versions take the full installer. Your projects, chats and settings are kept.

What's new in 2.44.0

  • A terminal or a browser beside your work. Two buttons in the title bar open a pane next to the page you are on: Terminal (Ctrl+`) and Browser (Ctrl+Shift+B). Drag the pane's edge to make it wider or narrower.
  • The browser pane. Tabs, an address bar that also searches, back, forward and reload. The pane has its own session that stays on your computer, so a site you sign in to there stays signed in. Forget sign-ins and site data clears it.
  • The agent can work in the browser pane. Ask for it in a Code task, for example "open the preview in the browser pane and try the form". The agent gets its own Agent tab beside your tabs and opens pages, clicks, types, reads and takes screenshots there, while you watch. It works in the pane's session, so it is signed in where you signed in. Its approval request says so: "in your browser pane, where your sign-ins are".
  • Thirteen built-in skills. They ship with Meevra Code and are on from the first start: video prompting, video editing with ffmpeg, Remotion, image generation, image editing, image upscaling, text in images, logo design in SVG, SVG quality, website design, model comparison, and two that choose the right image or video tool. The agent sees one line for each skill and reads a skill only when the task needs it. You find them in Marketplace > Skills with a Built in mark, and each can be turned off.
  • Keep computer awake. A switch in the title bar's More menu keeps the computer from sleeping while a long task runs. It lasts until you turn it off or close the app.
  • Current API prices. "What the API would charge" in Quota > Where it went uses the public list prices of 19 November 2026, for 217 models.

What came in 2.42.3

  • A new Chat never starts on a model you removed. When you disconnect a connection in Providers, a new Chat no longer opens on a model of that connection. It uses the same model as Code until you choose one.
  • A Chat you already used keeps its model. Its history stays as it was. The model is shown as not available until you choose another one.

What came in 2.42.2

  • A window that stays blank at start recovers by itself. If the app's page has not arrived 20 seconds after start, Meevra Code loads it again. If it still has not arrived, Meevra Code makes the window again once, and after that shows the window as it is, so you are never left with an invisible app. Each of these steps is written to the app's log.

Everything in Meevra Code

Work

  • Code. Describe a task once. A Lead plans, hands scoped work to helpers and integrates the result. The helper roles are Investigator (read only), Implementer (writes only inside the task's scope), Reviewer (read only), Diagnostician and Tester. A role's permissions are fixed: a prompt cannot give a read-only role the right to write.
  • Chat. A conversation with a model that has no access to your files and runs no commands.
  • Reply. Answer any message of a thread, with a quote, also while a task is running.
  • Approval levels. Every step asks before anything that changes something. Balanced lets everyday development run and still asks for network access, installs, screen control and changes outside the workspace. Full access runs every action without asking.
  • Checkpoints. Every step that changes files is saved, and you can rewind a session to any step.
  • A branch per session (optional). A Code session can work in its own Git worktree, so your checkout stays untouched until you merge. Nothing is forced and nothing is pushed.
  • Delivery. From a finished task to a pull request: Meevra Code pushes only the files the session's tasks changed, opens the pull request on GitHub, reads its checks and can send a failed check back to the agent. It asks you to confirm in its own window first. No model is used.
  • Race. Several models do the same task, each in its own copy of the project. Meevra Code shows measured facts for each one and a judge's opinion, with the model names shown only after it. You take one version or combine them file by file, and the tests run again.
  • Bots. Bots that tidy, summarise or digest your folders, with your approval.
  • Night shift. Queue a task for the night. It runs on plan quota that would otherwise be lost before the reset, never on a route that costs money.
  • Computer use. Agents can see the screen and use the apps you allow. It is off until you turn it on, the screen edges glow while it works, and Stop works at any moment.
  • Terminal. Run approved shell commands inside the app, on its own page or in a pane beside your work.
  • Browser pane. A browser with tabs beside your work. It keeps its sign-ins on your computer, and an agent can work in it when you ask.
  • Keep computer awake. A switch that keeps the computer from sleeping during a long task.

Checks that use no model

  • Proof it works. Before a task may end as done, Meevra Code runs your tests and your typecheck or build itself and shows the exact commands and their results.
  • Test truth. It checks whether the agent's new tests would fail without the change. A test that passes either way is marked "Doesn't check the change".
  • Claims checker. Every claim the agent makes at the end (tests passed, build OK, files changed, nothing left) is compared with Meevra Code's own records and shown as verified, not verified or contradicted.
  • Proof strength. In a temporary copy of your project Meevra Code makes one small break at a time in the changed lines and shows which breaks your tests noticed.
  • Error catcher. Errors from the commands, test runs and pages Meevra Code starts become cards mapped to your files, with Fix it.
  • Stuck detector. A task that goes in circles is paused early, with a plain explanation, before it burns your quota.
  • Promise. A running task shows how many turns and how much time tasks like it usually take, from your own record. A task that reaches twice its promise is held and asks you.
  • Reflexes. A finished task that was a set of commands can be saved and run again with no model at all.

See what is happening

  • Mission Control. Who works on what right now, the latest activity, and what waits for you.
  • Flow. Every project at work, drawn live: each agent, its model and speed, the file it works on and its tokens.
  • Activity. The audit trail of tasks, approvals, tests and provider events.
  • Quota. Plan limits and usage exactly as providers report them, a forecast, who used what, and Where it went: every model turn by model, effort, task and day, with what the API would charge for the same tokens.
  • Mobile. Pair your phone with a QR code and follow your tasks from it.
  • TV & second screen (experimental). Extend or mirror Meevra Code to a TV or a second screen.

Memory and knowledge

  • Brain. What Meevra Code remembers about your projects, chats and agents, stored on your computer. It learns from what really happened: a test command that ran and passed, a script that fails, what a finished task did. Agents get a small capsule of the memory that fits the task, as reference data and never as instructions.
  • Vault. Notes and reference text, encrypted on your computer, that you add to a chat or a task yourself.
  • Scout. A small, quick read-only helper that reads files for your agents, so the Lead's larger model does not spend its turns on reading.

Models and tools

  • Agents. A model, a reasoning effort and a prompt for each role. The model is Fixed, Preferred (your ordered list) or Auto. Each agent can have its own budget, and team presets can be saved, exported and imported.
  • Tools & MCP. The built-in tools and their rules, MCP servers, and a Marketplace of tools from the official MCP Registry.
  • Skills. Thirteen built-in skills for video, images, SVG, websites and model comparison, on from the first start. You can add your own or install more from GitHub. An agent reads a skill only when the task needs it.

Supported AI connections

Connection How you connect
Claude Code Sign in to Claude Code: Anthropic's own sign-in opens in its own window. Claude Code ships inside Meevra Code unmodified
ChatGPT Sign in to ChatGPT: OpenAI's own sign-in opens in your browser
Grok Build (xAI) xAI's own sign-in
Coding plans The plan's own key: Z.ai GLM Coding Plan, MiniMax M Plan, BytePlus ModelArk Coding Plan, StepFun Step Plan
Anthropic API, OpenAI API, OpenRouter, Xiaomi MiMo API key (OpenRouter also by sign-in)
Local models The built-in engine with a .gguf f...
Read more

Meevra Code 2.42.3

Choose a tag to compare

@MeevraCode MeevraCode released this 19 Nov 05:15

Meevra Code 2.42.3 - Public Preview

Meevra Code is an AI coding workspace for Windows. It works with the AI accounts you already have, keeps your work on your computer, and checks what its agents say they did. You open a project folder and describe what you want built, fixed or changed. A Lead agent plans and does the work with helper roles under your rules, and Meevra Code itself checks the result with real test runs before it calls anything done.

Download and install

  1. Download MeevraCode.exe below and run it. It installs Meevra Code on Windows 10 or Windows 11, 64-bit (x64).
  2. Read the license agreement and choose I Agree.
  3. Open Providers and connect at least one AI: a plan you sign in to, an API key, or a local model.

The preview installer is not code-signed yet, so Windows SmartScreen may show "Windows protected your PC". If you downloaded the installer from this page, choose More info, then Run anyway.

Already installed? You do not need this file. Meevra Code offers the update in Settings > Updates. An installed 2.42.2 takes this release as a small update (about 2 MB), and older versions take the full installer. Your projects, chats and settings are kept.

What's new in 2.42.3

  • A new Chat never starts on a model you removed. When you disconnect a connection in Providers, a new Chat no longer opens on a model of that connection. It uses the same model as Code until you choose one. Before this release a new Chat kept the removed model, and nothing could be sent from it.
  • A Chat you already used keeps its model. Its history stays as it was. The model is shown as not available until you choose another one.
  • Current API prices. "What the API would charge" in Quota > Where it went uses the public list prices of 18 November 2026, for 216 models.

Nothing else changed since 2.42.2.

What came in 2.42.2

  • A window that stays blank at start recovers by itself. If the app's page has not arrived 20 seconds after start, Meevra Code loads it again. If it still has not arrived, Meevra Code makes the window again once, and after that shows the window as it is, so you are never left with an invisible app. Each of these steps is written to the app's log.
  • A page that fails to load is written to the log in the installed app too, with the error's code and description.

What came in 2.42.1

  • Reply. Every message of a thread offers Reply, as in a chat app: an answer of the agent, a line it wrote during a task, a notice of Meevra Code itself, a Chat answer that failed. It works with every model, in Code and in Chat. Select a part of a message first and only that part is quoted.
  • Reply to a running task. A reply sent while a task is running reaches that task at its next step. Nothing is restarted.
  • The answer is marked. The agent's message that answers your reply says Answer to your reply and shows the words you quoted. Pressing the quote in a message you sent goes to the message it quotes.
  • Files a command wrote are counted in the task's changes, in a Git repository and in a folder with no Git.
  • Flow tells what happened. A step that never ran reads "not run", a stopped one "stopped", a denied one "denied". A task that waits for your answer reads "waiting for you".

Everything in Meevra Code

Work

  • Code. Describe a task once. A Lead plans, hands scoped work to helpers and integrates the result. The helper roles are Investigator (read only), Implementer (writes only inside the task's scope), Reviewer (read only), Diagnostician and Tester. A role's permissions are fixed: a prompt cannot give a read-only role the right to write.
  • Chat. A conversation with a model that has no access to your files and runs no commands.
  • Reply. Answer any message of a thread, with a quote, also while a task is running.
  • Approval levels. Every step asks before anything that changes something. Balanced lets everyday development run and still asks for network access, installs, screen control and changes outside the workspace. Full access runs every action without asking.
  • Checkpoints. Every step that changes files is saved, and you can rewind a session to any step.
  • A branch per session (optional). A Code session can work in its own Git worktree, so your checkout stays untouched until you merge. Nothing is forced and nothing is pushed.
  • Delivery. From a finished task to a pull request: Meevra Code pushes only the files the session's tasks changed, opens the pull request on GitHub, reads its checks and can send a failed check back to the agent. It asks you to confirm in its own window first. No model is used.
  • Race. Several models do the same task, each in its own copy of the project. Meevra Code shows measured facts for each one and a judge's opinion, with the model names shown only after it. You take one version or combine them file by file, and the tests run again.
  • Bots. Bots that tidy, summarise or digest your folders, with your approval.
  • Night shift. Queue a task for the night. It runs on plan quota that would otherwise be lost before the reset, never on a route that costs money.
  • Computer use. Agents can see the screen and use the apps you allow. It is off until you turn it on, the screen edges glow while it works, and Stop works at any moment.
  • Terminal. Run approved shell commands inside the app.

Checks that use no model

  • Proof it works. Before a task may end as done, Meevra Code runs your tests and your typecheck or build itself and shows the exact commands and their results.
  • Test truth. It checks whether the agent's new tests would fail without the change. A test that passes either way is marked "Doesn't check the change".
  • Claims checker. Every claim the agent makes at the end (tests passed, build OK, files changed, nothing left) is compared with Meevra Code's own records and shown as verified, not verified or contradicted.
  • Proof strength. In a temporary copy of your project Meevra Code makes one small break at a time in the changed lines and shows which breaks your tests noticed.
  • Error catcher. Errors from the commands, test runs and pages Meevra Code starts become cards mapped to your files, with Fix it.
  • Stuck detector. A task that goes in circles is paused early, with a plain explanation, before it burns your quota.
  • Promise. A running task shows how many turns and how much time tasks like it usually take, from your own record. A task that reaches twice its promise is held and asks you.
  • Reflexes. A finished task that was a set of commands can be saved and run again with no model at all.

See what is happening

  • Mission Control. Who works on what right now, the latest activity, and what waits for you.
  • Flow. Every project at work, drawn live: each agent, its model and speed, the file it works on and its tokens.
  • Activity. The audit trail of tasks, approvals, tests and provider events.
  • Quota. Plan limits and usage exactly as providers report them, a forecast, who used what, and Where it went: every model turn by model, effort, task and day, with what the API would charge for the same tokens.
  • Mobile. Pair your phone with a QR code and follow your tasks from it.
  • TV & second screen (experimental). Extend or mirror Meevra Code to a TV or a second screen.

Memory and knowledge

  • Brain. What Meevra Code remembers about your projects, chats and agents, stored on your computer. It learns from what really happened: a test command that ran and passed, a script that fails, what a finished task did. Agents get a small capsule of the memory that fits the task, as reference data and never as instructions.
  • Vault. Notes and reference text, encrypted on your computer, that you add to a chat or a task yourself.
  • Scout. A small, quick read-only helper that reads files for your agents, so the Lead's larger model does not spend its turns on reading.

Models and tools

  • Agents. A model, a reasoning effort and a prompt for each role. The model is Fixed, Preferred (your ordered list) or Auto. Each agent can have its own budget, and team presets can be saved, exported and imported.
  • Tools & MCP. The built-in tools and their rules, MCP servers, and a Marketplace of tools from the official MCP Registry.

Supported AI connections

Connection How you connect
Claude plan Anthropic's own sign-in in Claude Code, which ships inside Meevra Code unmodified
ChatGPT plan OpenAI's own sign-in in your browser
Grok Build (xAI) xAI's own sign-in
Coding plans The plan's own key: Z.ai GLM Coding Plan, MiniMax M Plan, BytePlus ModelArk Coding Plan, StepFun Step Plan
Anthropic API, OpenAI API, OpenRouter, Xiaomi MiMo API key (OpenRouter also by sign-in)
Local models The built-in engine with a .gguf file, Ollama, LM Studio, or an OpenAI-compatible server on your computer

Meevra Code never sees your password for a plan: you sign in with the maker's own sign-in. One account per provider can be connected in the preview. Meevra Code includes no model access of its own, resells nothing and adds nothing to what your provider charges.

Your quota and your money

  • Paid usage is Always ask by default. You can set a cap per task, per day or per month, or forbid paid APIs.
  • A task that reaches a limit pauses and asks. It never moves to something that costs more on its own.
  • A coding task is asked to finish in the fewest turns, and the turns after finished work run at a lower reasoning effort.
  • The checks above use no model, so they cost no tokens.

Privacy

  • No account with Meevra is needed, and no usage analytics are sent. Sharing anonymous usage totals is off until you turn it on.
  • Your projects, chats, settings, memory and API keys stay on your computer. Your prompts and files go only to the p...
Read more

Meevra Code 2.42.2

Choose a tag to compare

@MeevraCode MeevraCode released this 17 Nov 21:01

Meevra Code 2.42.2 - Public Preview

Meevra Code is an AI coding workspace for Windows. It works with the AI accounts you already have, keeps your work on your computer, and checks what its agents say they did. You open a project folder and describe what you want built, fixed or changed. A Lead agent plans and does the work with helper roles under your rules, and Meevra Code itself checks the result with real test runs before it calls anything done.

Download and install

  1. Download MeevraCode.exe below and run it. It installs Meevra Code on Windows 10 or Windows 11, 64-bit (x64).
  2. Read the license agreement and choose I Agree.
  3. Open Providers and connect at least one AI: a plan you sign in to, an API key, or a local model.

The preview installer is not code-signed yet, so Windows SmartScreen may show "Windows protected your PC". If you downloaded the installer from this page, choose More info, then Run anyway.

Already installed? You do not need this file. Meevra Code offers the update in Settings > Updates. An installed 2.42.1 takes this release as a small update (about 2 MB), and older versions take the full installer. Your projects, chats and settings are kept.

What's new in 2.42.2

  • A window that stays blank at start recovers by itself. If the app's page has not arrived 20 seconds after start, Meevra Code loads it again. If it still has not arrived, Meevra Code makes the window again once, and after that shows the window as it is, so you are never left with an invisible app. Each of these steps is written to the app's log.
  • A page that fails to load is written to the log in the installed app too, with the error's code and description.
  • Closing a recovered window ends the app as usual.
  • Current API prices. "What the API would charge" in Quota > Where it went uses the public list prices of 17 November 2026, for 216 models.

Nothing else changed since 2.42.1.

What came in 2.42.1

  • Reply. Every message of a thread offers Reply, as in a chat app: an answer of the agent, a line it wrote during a task, a notice of Meevra Code itself, a Chat answer that failed. It works with every model, in Code and in Chat. Select a part of a message first and only that part is quoted.
  • Reply to a running task. A reply sent while a task is running reaches that task at its next step. Nothing is restarted.
  • The answer is marked. The agent's message that answers your reply says Answer to your reply and shows the words you quoted. Pressing the quote in a message you sent goes to the message it quotes.
  • Files a command wrote are counted in the task's changes, in a Git repository and in a folder with no Git.
  • Flow tells what happened. A step that never ran reads "not run", a stopped one "stopped", a denied one "denied". A task that waits for your answer reads "waiting for you".

Everything in Meevra Code

Work

  • Code. Describe a task once. A Lead plans, hands scoped work to helpers and integrates the result. The helper roles are Investigator (read only), Implementer (writes only inside the task's scope), Reviewer (read only), Diagnostician and Tester. A role's permissions are fixed: a prompt cannot give a read-only role the right to write.
  • Chat. A conversation with a model that has no access to your files and runs no commands.
  • Reply. Answer any message of a thread, with a quote, also while a task is running.
  • Approval levels. Every step asks before anything that changes something. Balanced lets everyday development run and still asks for network access, installs, screen control and changes outside the workspace. Full access runs every action without asking.
  • Checkpoints. Every step that changes files is saved, and you can rewind a session to any step.
  • A branch per session (optional). A Code session can work in its own Git worktree, so your checkout stays untouched until you merge. Nothing is forced and nothing is pushed.
  • Delivery. From a finished task to a pull request: Meevra Code pushes only the files the session's tasks changed, opens the pull request on GitHub, reads its checks and can send a failed check back to the agent. It asks you to confirm in its own window first. No model is used.
  • Race. Several models do the same task, each in its own copy of the project. Meevra Code shows measured facts for each one and a judge's opinion, with the model names shown only after it. You take one version or combine them file by file, and the tests run again.
  • Bots. Bots that tidy, summarise or digest your folders, with your approval.
  • Night shift. Queue a task for the night. It runs on plan quota that would otherwise be lost before the reset, never on a route that costs money.
  • Computer use. Agents can see the screen and use the apps you allow. It is off until you turn it on, the screen edges glow while it works, and Stop works at any moment.
  • Terminal. Run approved shell commands inside the app.

Checks that use no model

  • Proof it works. Before a task may end as done, Meevra Code runs your tests and your typecheck or build itself and shows the exact commands and their results.
  • Test truth. It checks whether the agent's new tests would fail without the change. A test that passes either way is marked "Doesn't check the change".
  • Claims checker. Every claim the agent makes at the end (tests passed, build OK, files changed, nothing left) is compared with Meevra Code's own records and shown as verified, not verified or contradicted.
  • Proof strength. In a temporary copy of your project Meevra Code makes one small break at a time in the changed lines and shows which breaks your tests noticed.
  • Error catcher. Errors from the commands, test runs and pages Meevra Code starts become cards mapped to your files, with Fix it.
  • Stuck detector. A task that goes in circles is paused early, with a plain explanation, before it burns your quota.
  • Promise. A running task shows how many turns and how much time tasks like it usually take, from your own record. A task that reaches twice its promise is held and asks you.
  • Reflexes. A finished task that was a set of commands can be saved and run again with no model at all.

See what is happening

  • Mission Control. Who works on what right now, the latest activity, and what waits for you.
  • Flow. Every project at work, drawn live: each agent, its model and speed, the file it works on and its tokens.
  • Activity. The audit trail of tasks, approvals, tests and provider events.
  • Quota. Plan limits and usage exactly as providers report them, a forecast, who used what, and Where it went: every model turn by model, effort, task and day, with what the API would charge for the same tokens.
  • Mobile. Pair your phone with a QR code and follow your tasks from it.
  • TV & second screen (experimental). Extend or mirror Meevra Code to a TV or a second screen.

Memory and knowledge

  • Brain. What Meevra Code remembers about your projects, chats and agents, stored on your computer. It learns from what really happened: a test command that ran and passed, a script that fails, what a finished task did. Agents get a small capsule of the memory that fits the task, as reference data and never as instructions.
  • Vault. Notes and reference text, encrypted on your computer, that you add to a chat or a task yourself.
  • Scout. A small, quick read-only helper that reads files for your agents, so the Lead's larger model does not spend its turns on reading.

Models and tools

  • Agents. A model, a reasoning effort and a prompt for each role. The model is Fixed, Preferred (your ordered list) or Auto. Each agent can have its own budget, and team presets can be saved, exported and imported.
  • Tools & MCP. The built-in tools and their rules, MCP servers, and a Marketplace of tools from the official MCP Registry.

Supported AI connections

Connection How you connect
Claude plan Anthropic's own sign-in in Claude Code, which ships inside Meevra Code unmodified
ChatGPT plan OpenAI's own sign-in in your browser
Grok Build (xAI) xAI's own sign-in
Coding plans The plan's own key: Z.ai GLM Coding Plan, MiniMax M Plan, BytePlus ModelArk Coding Plan, StepFun Step Plan
Anthropic API, OpenAI API, OpenRouter, Xiaomi MiMo API key (OpenRouter also by sign-in)
Local models The built-in engine with a .gguf file, Ollama, LM Studio, or an OpenAI-compatible server on your computer

Meevra Code never sees your password for a plan: you sign in with the maker's own sign-in. One account per provider can be connected in the preview. Meevra Code includes no model access of its own, resells nothing and adds nothing to what your provider charges.

Your quota and your money

  • Paid usage is Always ask by default. You can set a cap per task, per day or per month, or forbid paid APIs.
  • A task that reaches a limit pauses and asks. It never moves to something that costs more on its own.
  • A coding task is asked to finish in the fewest turns, and the turns after finished work run at a lower reasoning effort.
  • The checks above use no model, so they cost no tokens.

Privacy

  • No account with Meevra is needed, and no usage analytics are sent. Sharing anonymous usage totals is off until you turn it on.
  • Your projects, chats, settings, memory and API keys stay on your computer. Your prompts and files go only to the provider you chose.
  • The update check sends only the app's version and edition. Every update is verified before it is installed.

Known limits

  • Outside a Git repository a task that ran a program ends as "Needs a look", not Done: without a repository Meevra Code cannot prove what the program changed.
  • Sessions made before 2.42.1 show no "Answer to your reply" mark on their old messages.
  • A Chat answer on the...
Read more

Meevra Code 2.42.1

Choose a tag to compare

@MeevraCode MeevraCode released this 17 Nov 11:10

Meevra Code 2.42.1 - Public Preview

Download MeevraCode.exe and run it to install Meevra Code on Windows (x64). Installed copies check for updates and offer them in Settings > Updates: an installed 2.41.0 takes this release as a small update (about 3 MB).

What's new since 2.41.0

  • Reply. Every message of a thread offers Reply, as in a chat app: an answer of the agent, a line it wrote during a task, a notice of Meevra Code itself, a Chat answer that failed. It works with every model, in Code and in Chat. Select a part of a message first and only that part is quoted.
  • Reply to a running task. A reply sent while a task is running reaches that task at its next step. Nothing is restarted.
  • The answer is marked. The agent's message that answers your reply says Answer to your reply and shows the words you quoted. Pressing the quote in a message you sent goes to the message it quotes.
  • Files a command wrote are counted. A file written by a program the task ran is listed with the run that wrote it and counted in the task's changes, in a Git repository and in a folder with no Git.
  • Flow tells what happened. A step a stopped task never ran reads "not run", a stopped one "stopped", a denied one "denied", never "done". A task that waits for your answer reads "waiting for you".
  • Task started on names the model the task's Lead runs on.

Known limits: outside a Git repository a task that ran a program ends as "Needs a look", not Done, because without a repository Meevra Code cannot prove what the program changed. Sessions made before this version show no "Answer to your reply" mark on their old messages.

The full list is in the changelog, and every feature is described in the README.

Meevra Code is free to use under the End User License Agreement (EULA-en.txt). Open-source components are listed with their licenses in THIRD-PARTY-NOTICES.txt.

Meevra Code 2.41.0

Choose a tag to compare

@MeevraCode MeevraCode released this 16 Nov 04:03

Meevra Code 2.41.0 - Public Preview

Download MeevraCode.exe and run it to install Meevra Code on Windows (x64). Installed copies check for updates and offer them in Settings > Updates: an installed 2.38.10 takes this release as a small update (about 3 MB).

What's new since 2.38.10

  • Delivery. A new row under a Code session's task pushes the session's change, opens the pull request and reads its checks. Meevra Code does it itself, with no model, and asks you to confirm before anything leaves your computer. When a check fails, one button sends the failed checks to the agent, and another pushes the fix to the same pull request.
  • Where it went. A new tab on the Quota page: every model turn is recorded, shown by model, reasoning effort, who used it, task and day, with what the API would charge for the same tokens.
  • Proof strength. After a task's tests pass, Meevra Code checks by itself whether those tests would notice a small mistake in the change. No model is used.
  • Reflexes. A finished task of commands can be saved and run again with no model and no plan quota. If a step ends differently, the model takes over.
  • Promise. A running task is promised its turns and time from your own record of finished tasks, and is held when it reaches twice that.
  • Night shift. Queued tasks run in the hours you set, on plan quota that would otherwise be lost, never on a route that costs money.
  • Computer use is much faster, brings the task's window to the front, and used about 59 percent fewer tokens on our measured task.
  • Fewer turns. On our two measured coding tasks, about 43 percent and about 24 percent fewer tokens, with every test passed.
  • Full access asks nothing, with every model, and stays chosen after a restart.

The full list is in the changelog, and every feature is described in the README.

Meevra Code is free to use under the End User License Agreement (EULA-en.txt). Open-source components are listed with their licenses in THIRD-PARTY-NOTICES.txt.

Meevra Code 2.38.10

Choose a tag to compare

@MeevraCode MeevraCode released this 12 Nov 14:39

Meevra Code 2.38.10 - Public Preview

Download MeevraCode.exe and run it to install Meevra Code on Windows (x64). Installed copies check for updates and offer them in Settings > Updates.

Meevra Code is free to use under the End User License Agreement (EULA-en.txt). Open-source components are listed with their licenses in THIRD-PARTY-NOTICES.txt.

Meevra Code 2.38.9

Choose a tag to compare

@MeevraCode MeevraCode released this 12 Nov 08:08

Meevra Code 2.38.9 - Public Preview

Download MeevraCode.exe and run it to install Meevra Code on Windows (x64). Installed copies check for updates and offer them in Settings > Updates.

Meevra Code is free to use under the End User License Agreement (EULA-en.txt). Open-source components are listed with their licenses in THIRD-PARTY-NOTICES.txt.