NATIVE TERMINAL FOR MACOS

Your Macs.
One terminal
workspace.

TerminalDB brings your shell, command history, project tools, and Claude assistance into one macOS workspace. Work locally or choose a paired Mac over your LAN or VPN.

macOS 13+ · Apple Silicon (M1 or later) · Free & open source
Current builds are not notarized.

REAL NATIVE APP Fictional demo data
TerminalDB on macOS with the execution workstation visible in the toolbar and terminal tab.
Your shell and tools run on the Mac you choose.
01

Local by defaultA new tab opens on This Mac.

02

Sessions stay putClose the view. Come back to your shell.

03

Share by choicePair devices. Approve account sync separately.

YOUR WORKSTATIONS

Leave the Mac.
Keep the terminal.

Start here. Continue on another Mac. Commands and tools run on the workstation you select, and its name stays visible while you work.

  1. 1

    Pair once, on your LAN

    Open Add Mac on both computers. Compare the complete fingerprints and approve on both screens.

  2. 2

    Choose where to work

    New tabs open locally. Use the workstation menu for a new terminal or an existing session on another Mac.

  3. 3

    Reconnect to the same shell

    Closing a tab or quitting the app disconnects its view. End Session explicitly stops the shell and its work.

One session. More than one view.

Attach without changing another Mac's selected tab. Multiple viewers can watch; Take Control transfers typing and resizing to one person at a time.

Built for the lid-close moment.

Your session stays on its original Mac while your viewing laptop sleeps. Wake your laptop and reconnect over your LAN or VPN to continue.

At home on your network.

LAN connections stay local and work without internet. Away from home, connect your own VPN. Save an internal address when discovery does not cross the VPN.

The execution Mac must stay powered on, awake, and logged in. Sessions survive app exits and network interruptions, but end on reboot, logout, or session-host failure. Files stay on their workstation.

CLAUDE ACCOUNTS

Your subscriptions.
Ready on your Macs.

One account list for This Mac and the Macs you choose to sync. Select a subscription for the tab you're viewing, whether its shell runs here or on another workstation.

AWS ACCESS

Your profiles.
Fewer sign-ins.

TerminalDB detects SSO and console-login profiles in ~/.aws/config. Sign in when AWS asks, then keep working with Ready profiles while TerminalDB handles renewal. One browser sign-in renews the SSO session for all local profiles that use it.

How AWS sharing works
AWS AccessThis Mac

developmentDetected SSO profile

Sign In

productionShared by an approved Mac

Ready

Illustration. Your own profile names appear in the app.

  • Use familiar names, or choose a local alias.
  • Review name conflicts before changing a profile.
  • Approve AWS sharing separately on both Macs.

Choose what to share. Only profiles you select share temporary AWS credentials, including through other explicitly approved AWS-sync Macs. AWS login and refresh material stays with the official AWS CLI on the Mac where you sign in. On a receiving Mac, choose Use on This Mac once.

Ready, with renewal handled. TerminalDB renews selected access in the background and sends updates to approved connected Macs. Received access stays usable while the source Mac is offline, until AWS expires it. Profiles are grouped by SSO session, with Sign In and the session's end time on its header. Each profile shows one status line and a button only when there is something to do. Check Access is in its actions menu; AWS controls the lifetime, and a check does not reset it.

ACCOUNTS & USAGE

Know what you're using.
See what's left.

Your selected Claude account stays in the status bar. Open Usage & Settings when you want allowance, burn, forecast, and reset details.

Useful numbers, honest status

Usage shows freshness. Stale or unavailable data is clearly marked instead of presented as current quota.

A subscription or your API key

Use a Claude subscription for supported Claude Code requests, or configure an Anthropic API key separately. API billing and subscription allowances remain distinct.

YOUR EVERYDAY TERMINAL

A terminal worth staying in.

Native tools around your shell, with execution kept on the selected workstation.

Command ledger & history

Find completed commands, inspect output, and return to useful work without losing the terminal in front of you.

Claude at hand

Ask about selected output and project context. Review proposed commands and patches before applying them.

Tabs, splits & workspaces

Save layouts and workstation references. An unavailable session returns as a reconnectable placeholder.

Project tools

Inspect Git changes, browse project files, and run test actions where the project actually lives.

Monitors & playbooks

Follow running commands and turn repeatable steps into workflows you can preview and approve.

Your native preferences

Keep appearance and keyboard preferences on the Mac you're using, while execution and project data stay with the host.

PRIVATE BY DESIGN

Private connections.
Between your Macs.

Your terminals connect directly to paired Macs over your LAN or VPN. You choose which devices connect and which accounts they share.

Read the security model
01

Recognize the Mac you trust.

Compare the full fingerprints and approve on both Macs. Connections use TLS 1.3 with mutually verified, pinned device keys.

02

Choose which accounts you share.

Pairing allows workstation access. You approve Claude and AWS sharing separately on both Macs.

03

Stay in control of access.

A paired Mac has powerful access to terminals and tools under your macOS user. Remove a Mac to block it here. Stopping sync blocks additional transfers; revoke credentials at the provider to invalidate existing copies.

Security depends on verified pairing, correct implementation, and uncompromised Macs. Claude and AWS sign-in and requests, plus software updates, use their respective services. Terminal connections go directly to your configured Macs.

GET STARTED

At home on your Mac.

Free, MIT licensed, and actively developed. For Apple Silicon Macs, M1 or later, running macOS 13 Ventura or later.

  1. 1

    Download and move to Applications.

    Unzip TerminalDB-macOS.zip, then move TerminalDB to your Applications folder.

    Updating from 0.6.7 or earlier? Use this download for a one-time manual update. Finish active terminal work, quit TerminalDB, then replace your copy in Applications. Those versions cannot install this update in the app; in-app updates work from the new version.

  2. 2

    Allow the first launch.

    The current release is not notarized. Verify the GitHub download and published SHA-256 checksum. If macOS blocks it, use System Settings → Privacy & Security → Open Anyway.

  3. 3

    Start local. Add your other Macs when ready.

    A terminal opens on This Mac. Install on another Mac and use Manage Macs → Add Mac to pair. Allow the requested background activity and Local Network access.

A FEW PRACTICAL DETAILS

Clear answers.
Fewer surprises.

Do I need an account to use TerminalDB?

TerminalDB works without an account. Start a local terminal immediately and pair your other Macs when you choose. Claude and AWS features use your existing provider accounts and need internet for provider sign-in and requests.

What happens when I close my laptop?

Its views disconnect. Work on another awake, logged-in Mac continues in that Mac's session host. Wake your laptop and restore LAN or VPN connectivity to reconnect. A sleeping execution Mac cannot keep commands running; reboot, logout, or session-host failure ends its sessions.

Can I use this away from my LAN?

Yes, through your own VPN with a route to the execution Mac's private network. Pair initially on the same LAN. If Bonjour discovery does not cross your VPN, save the paired Mac's internal IP address or internal DNS name in its Connection settings. TerminalDB does not set up your VPN, forward router ports, relay traffic, or synchronize files.

How do accounts sync when I return home?

A reusable Claude sign-in works on the Mac where you add it and syncs to your approved Macs when LAN or VPN connectivity returns. Renewals and removals also sync on reconnect. Ordinary local Claude sign-ins need the one-time Share Sign-In flow before they can sync.

What if two Macs have different AWS profiles, or the same profile name?

TerminalDB detects each Mac's supported profiles. Shared identity includes the provider, account, and role or principal; a matching name alone is not enough. On a receiving Mac, keep a familiar name or choose an alias. Review conflicts before a local profile changes. Unrelated profiles stay untouched.

Can AWS access work while the source Mac is offline?

Yes, until the temporary credentials expire. AWS requests still need a network connection to AWS. Fresh shared credentials need a reachable approved Mac with usable AWS access. TerminalDB handles renewal and synchronization automatically. Check Access is in each profile's actions menu. If fresh shared access is unavailable, choose Sign In Here in the same menu to make this Mac a source. Receiving tools must support AWS's credential_process interface. A managed same-name profile uses TerminalDB's sign-in controls; a separate alias preserves your original AWS login command.

Does unpairing revoke every account credential?

No. It blocks that Mac on this host and stops future transfers. It cannot erase an offline copy or revoke a token already held by another process. Revoke access with Claude or AWS when immediate invalidation is required. Pairing with one Mac does not authorize access to all of its peers.

How does Claude account sharing work?

TerminalDB shares explicitly enabled reusable tokens, stored in each approved Mac's device-only Keychain. Ordinary rotating Claude login and refresh credentials stay local. Claude.ai connectors require a normal local sign-in. Restart Claude after renewing a shared sign-in. Provider-side expiry or revocation applies.