What are you building with NEXO?

[wazionapps]

We'd love to hear how you're using NEXO Brain in your daily workflow!

• What kind of tasks do you delegate to NEXO?
• Which tools/MCPs have you connected?
• Any unexpected use cases you've discovered?

Share your setup, wins, and lessons learned. Whether you're using it for code review, email automation, project management, or something completely different — we want to know! 🧠

[wazionapps]

Week-in-review (2026-04-20) — Team update from the NEXO core

Posting the weekly rollup of what NEXO (the AI co-operator) and I have been shipping together, so you can see the pace and the pattern.

Since the last update (April 7 → April 20):

• v7.0.0 / v7.1.0 — Plan Consolidado F0.6 (BREAKING): physical layout split between Brain (the shared-memory engine) and Desktop (the macOS UI). The two are now clean, independently releasable surfaces. Migration notes inside the release.
• v6.5.0 — Brain/Desktop separation disclaimer: every surface now clearly says "this is Brain" or "this is Desktop" so new users don't confuse them on install.
• v6.4.0 — multi-tenant email accounts: the email pipeline (daemon, monitor, followup-runner) now supports multiple accounts per operator. First big step toward agency/team usage.
• v6.3.1 — privacy hotfix: tightened what the email classifier logs. No PII in run logs unless explicitly opted in.
• v6.0.x stability run: installer no longer leaks NEXO_HOME / bin into shell profiles; strict hook contract on unknown targets; pytest suite wired into CI.

Under the hood (not a release, but shipped):

• Deep scan at onboarding — "know the user" run that builds a profile before the first real ask, so NEXO doesn't start cold.
• REPO_DIR resolution fix (no more phantom clones).
• Headless permission boundaries — the followup-runner explicitly refuses interactive-only operations and escalates priority after N consecutive skips, instead of silently deferring forever.
• Operator alias recognition — if a script was created by operator X and session Y invokes it, NEXO now treats them as the same identity across terminals (Claude Code + Codex + Desktop).

What I'm curious about from you:

• If you're self-hosting NEXO Brain, what's your daily driver surface — Claude Code, Codex, Desktop, or something else?
• For the multi-tenant email work (v6.4.0), is agency-style usage (many customer inboxes under one operator) something you'd actually turn on?

Reply here or open a new discussion. I'll keep doing a Monday rollup.

— NEXO + Francisco