v0.4.5

See what Nectra saves you

After each chat answer, Nectra shows what the conversation has cost so far at API list prices, next to the same tokens at Opus prices:

This chat: $0.005 at API prices; the same tokens at opus prices: $0.18.

nectra usage now has a COST column and the same comparison over all your chats. It also counts model switches, handoff notes and /again retries. --baseline MODEL compares against another model.

nectra usage --direct adds the Claude Code and Codex sessions you ran without Nectra, with the cost per turn on each side. To compare for yourself, use Nectra for some of your work and the CLIs directly for the rest, then run nectra usage --days 14 --direct.

Costs are list prices for the same tokens. Plans don't bill per token, and they don't publish how much each model uses. Treat the numbers as a yardstick, not a bill.

What Nectra does on your machine

docs/trust.md lists what Nectra reads, writes and sends, and what each provider's terms say about tools like it. In short:

• Nectra runs each provider's own CLI under your login and never touches your credentials.
• Anthropic's consumer terms restrict scripted use of Pro and Max plans. Stream view and handoff notes use claude -p. The page says how to avoid that.

Changes

• Gemini CLI uses stream view. Since 0.64, Gemini loads per-launch settings only from files an administrator owns, so Nectra can't add the hooks its terminal view needs.
• nectra mcp --sync writes each CLI's config itself. Each CLI's own mcp add takes environment values, often tokens, as command-line arguments, which other users on the machine can see. Nectra now writes each config file directly. It keeps the file's permissions and won't overwrite a file that changed during the sync.
• nectra usage works while a chat is open. On Windows it used to fail. An open chat's own usage is left out, and the report says so.
• The reference docs are accurate again about cooldowns (they persist across restarts), how the conversation is sent (sessions resume), and CI.

Chat logs written by 0.4.5 can't be opened by Nectra 0.4.4 or older.

For contributors

scripts/compat/schedule.ps1 runs the CLI compatibility check daily on a Windows PC, against the CLIs you actually use, and shows a notification if anything fails.

The macOS builds are still cross-compiled and haven't run on a real Mac yet. Please open an issue if anything breaks.