EVA CODE · MACOS PREVIEW 0.8.0

Build with the hosted Eva API.

This Apple Silicon app connects to the same Eva Developer API at goai.evax.live/developers. Requires macOS 14 or later. No local GOAI installation or Node setup is needed.

Install and sign in

  1. Open the disk image and drag Eva Code to Applications.
  2. Open the app and select Continue to Sign In.
  3. Use your existing GOAI email/password, or choose Create a free account. Passwords require at least 15 characters.
  4. Create a workspace, describe a small Python program, review the proposed changes, and apply them.

Trial and EvaXCoding subscription

New accounts receive $10 in shared trial usage credit with no card required. EvaXCoding is $19.99 per month and includes a fresh $40 usage allowance each paid billing month. The allowance resets on renewal and does not roll over. After it is used, successful generations are metered at half the current GPT-6.1 Sol standard token rates: $1 per million input tokens, $0.05 per million cached input tokens when the service reports them, and $5 per million output tokens. Subscribe or manage billing in the Eva Developer console.

The API reserves credit before generation and enforces exhaustion. Completed API generations consume credit even if their code proposal cannot be parsed or applied. Failed requests release credit; uncertain requests keep it reserved until resolved. Stopping the desktop request may not stop work already running on the API. In Build & verify mode, you approve a limit of one to six API requests. Failed verification or an invalid completed edit response can use the next approved request. Network errors and uncertain submissions are not automatically retried.

Edit code yourself

Select a file to edit it with syntax highlighting, line numbers, search/replace, undo and redo. Drafts stay in memory while switching files. Select Review changes (or ⌘S), inspect the diff, then Apply reviewed changes to save. Editing uses no API credit. Save before asking Eva or running code. Unsaved drafts are not crash recovery backups.

Build and verify (experimental)

Choose Build & verify, set a limit of one to six requests, and enter a Python verification command. Docker must be running before generation. For multi-file tasks Eva first plans the work, then writes one file at a time and runs that fixed command on a temporary copy. Planning counts toward your request limit; four requests is the default. The agent stops early when all planned files and verification pass. It can use the remaining requests to repair failures. Review the final diff before applying. Existing files under test/ or tests/, Python files named test*.py or *_test.py, and conftest.py cannot be changed by Build & verify. Use manual editing or Propose changes to intentionally update those files first. New Python tests must import or launch project code; duplicated implementation definitions are rejected. If unittest discovers no tests, Eva can add a test file within your request limit. A standard python -m unittest command reporting zero tests does not count as successful verification. A passing command is not proof of correctness; choose tests that exercise your requirements. Live model responses can still fail to produce usable edits.

Bring a small project

Import folder copies up to 40 text files, 32 KiB per file and 128 KiB total; hidden, generated, binary and common credential files are skipped. Review your files before sending. This does not sync with the original folder. Export project JSON saves an archive of the current editor files. Undo last save restores the previous saved snapshot.

Eva receives a file manifest and selected whole files within its input budget. The result shows included and omitted file counts. Files outside the selected context cannot be edited. Name important files in your request; large files may need splitting.

Run Python locally

Install and start Docker Desktop. Install the pinned Python image once:

docker --context desktop-linux pull python@sha256:c4634f578a412db396771b61b064c6e546c9d6414c7fb5b1b05d5871f1885f7b

Local commands consume no API credit. Code runs in an isolated Linux container with no network or host-directory mounts. The CLI must be available at /usr/local/bin/docker with the desktop-linux context. Changes made inside commands are temporary; durable edits use review/apply.

Files and account security

Workspace files and optional task history stay in ~/Library/Application Support/Eva Code, scoped to your hosted account. Pressing Send transmits the selected workspace and recent conversation to the hosted Eva API. This is separate from GOAI's legacy local preview store; prior local-preview workspaces are not imported automatically.

Passwords, hosted cookies, and API keys are kept only in memory. The app creates a labeled key for this installation and revokes it on sign-out or graceful quit. After a crash or network outage, cleanup is retried at the next sign-in on the same installation. You can revoke any leftover key in the developer console. No model admission key or Stripe secret is bundled.

Signing out preserves local files. Deleting a hosted account invalidates access but does not remotely erase copies already on your Mac. Remove tasks/workspaces in the app or remove the local data folder if you want to delete those copies. Uninstalling the app does not delete the data folder.

Preview release

This build is ad-hoc signed for local testing, not Developer ID signed or notarized. Keep macOS security protections enabled. Public distribution still needs Apple release signing and notarization. Windows and Intel Mac builds are not included.

Git repositories and acceptance checks

Choose Open Git repository to select a checkout with an existing commit. Eva supports up to 40 eligible text files, 32 KiB each, 128 KiB total. Search matches file paths and code. Review and save edits in Eva, then use Review write to repository and confirm the exact diff to write them back. Git staging, commits, and pushes remain under your control.

Outside file edits or branch changes require reloading repository files before writing. Undo last save restores the previous Eva snapshot; a separate reviewed write restores those files in the checkout. Hidden, binary, generated and credential paths are excluded.

Build & verify can also run an additional acceptance command after the primary command succeeds. Passing commands do not guarantee that every requirement is covered. Generating extra requirement tests remains an internal experiment. Exact-patch generation is not enabled in this release; model correctness remains a limitation.