01 / THE WORKSPACEActual app capture · local development example
A local development example
One fix. The whole stack in view.
A frontend and worker in one folder. An API in another. Follow a failing health check through a source correction and three passing HTTP contract tests.
NATIVE APP RECORDING · SCRIPTED ACTIONS · SILENTDownload video ↓What this recording proves
Four actual terminal sessions run a local web server, HTTP API, worker, and tests among fourteen example project folders. The API health route initially returns 503. A scripted source correction changes it to 200; three HTTP contract tests pass, and the related task is marked done. Other tasks remain visible. The worker processes three local jobs.
Actions are scripted in the real native app. This example uses no customer data, deployed service, or authenticated coding-agent turn. Named workspace switching, automatic agent attention badges/sounds, and provider-aware conversation resume are planned features.
Less time finding your place.
Different folders. One working context.
Keep an API beside its frontend. See the remaining tasks alongside the terminal. Leave a clear next step for when you come back.
One workspace. A few useful tools.
02 / APPS
Your projects, within reach.
Find an app, choose its context, and keep your terminals in place. Fourteen example projects, with a live web app, API, worker, and tests.
Built around the daily loop
From a loose thought to the next thing shipped.
01
Bring your work together
Discover projects in your common work folders, add one with a click, and launch real shell or installed coding CLI sessions. Each terminal keeps its own process.
02
Turn the notes into a plan
Capture a task quickly, or review tasks extracted from local Markdown and text. Keep the source and undo an import batch.
03
Keep an eye on the app
Check HTTP health and see when each sample was observed. A Sentry connector can turn issues into tasks; live-account verification is still pending.
04
Keep the conversation nearby
Link a local Codex transcript for read-only context. Continue the conversation in its original session.
⌘
Mac first
Native SwiftUI and embedded terminals. Keyboard shortcuts for finding work, adding tasks, and importing notes.
↗
Space to focus
Move, resize, zoom, or focus a panel. Collapse tool labels when you want more room for the work.
○
Local by default
Workspace data stays on your Mac. Sentry tokens use macOS Keychain. Connected services receive the requests you configure.
A preview with the details in the open
Know what you’re trying.
Useful today. Still being tested. Here is the evidence behind this build, and the work left before a public release.
01 / VERIFIED LOCALLY
Real work. Visible results.
The recording shows four actual terminals across fourteen example projects: a web app, API, worker, and tests. An HTTP 503 becomes a 200 after a source fix.
Apple Silicon code is included, but hardware testing is pending. macOS 14 runtime, live Sentry, and long-running terminal sessions also need validation.
Tasks, notes, layout, and project paths are saved locally. Sentry tokens use macOS Keychain. Configured health endpoints, Sentry, and coding CLIs can make network requests.
The ZIP contains both x86_64 and arm64 code. This build was run on an Intel Mac with macOS 15.7.7. Apple Silicon hardware and the minimum supported macOS 14 still need runtime testing. Universal packaging alone does not prove compatibility.
What happens to my terminals when I quit?
Saved commands, folders, tasks, notes, and layout persist. Running terminal processes and their output do not survive quitting. Neovibe asks before stopping active terminals. Continue an existing coding conversation through that provider’s own session tools.
Is health checking production uptime monitoring?
Checks run while Neovibe is open and show observed HTTP samples. They are useful for development, but do not replace an independent production uptime monitor.
Is this a finished public release?
No. This is a private evaluation build, locally signed and not notarized by Apple. macOS may block it or show a warning. A verified distribution identity, public support channel, and final release terms are not available yet. Use the recording and screenshots to evaluate the workflow if you prefer to wait.
Which features are still planned?
Named workspace switching, moving work between workspaces, automatic agent attention badges and sounds, and provider-aware conversation resume remain planned. The screenshots show the current single-canvas workflow.
Does Neovibe collect analytics or upload my projects?
This build includes no Neovibe analytics, hosted account service, or automatic crash uploads. Project suggestions inspect folder names and metadata locally. Programs you run in terminals follow their own network and privacy settings. This website uses local assets and no third-party scripts.
Neovibe 0.4.0 · build 7
Make room for better work.
Explore the current build at your own pace. No Neovibe account or subscription required for this preview.