>_GOLDEN TERMINAL
GOLDEN TERMINAL · CONTROLLED AI ACCESS

Give your AI hands.

Golden connects the AI you already use to your authorized computers, servers and tools.

Stop Ctrl-C/Ctrl-V. Let’s Golden.

YOUR AI · GOLDEN · YOUR MACHINES
YOUR AI ↔ GOLDEN ↔ YOUR ENVIRONMENT
AI ENTHUSIASTS

Don't know how?Let your AI help.

A broken Windows PC. A router acting up. A new server you don't know how to configure.

Use the AI you already trust to investigate real problems on the machine, instead of spending hours copying commands and searching for answers.

EXPLORE EVERYDAY FIXES
HANDS-ON IT PROS

Know how. Tired?Stop doing it manually.

You already know the commands. But checking logs, diagnosing failures and repeating terminal operations takes time.

Let your AI inspect, execute and verify using the tools already available in your environment. You stay responsible for the decisions.

EXPLORE TECHNICAL WORKFLOWS
KEEP YOUR AI · REACH THE NEXT MACHINE

Already using Codex or Claude Code? Great. Keep it.

If your AI already works perfectly on your development machine, you may not need Golden there.

Now try another computer. A family PC. An office workstation. A new machine where your usual AI setup doesn't exist.

Golden gives your compatible AI a way to work in that environment without setting up an entire new development stack.

TEMPORARY TERMINAL SESSION

Open. Connect. Ask. Close.

Open Golden Terminal when you need it. Connect your compatible AI, complete the task, then close the terminal to disconnect.

No permanent background agent required for supported Terminal Session Mode.

Foreground Terminal Session Mode is available for Windows and macOS. Commands run with the permissions of the terminal user. Closing the session stops new commands, but does not undo completed actions.

HOW TO CONNECT
WHAT HAPPENS AFTER CONNECT GOLDEN?

Connect Golden. Bring this device online. Ask normally.

Your AI stays in ChatGPT or another MCP-compatible client. Golden connects that AI to one live customer runtime, and the local Session / Agent is the execution point on the machine.

01 · CONNECT GOLDEN

Install your AI connection.

In ChatGPT, use Plugins → + → Add custom MCP server, enter Golden's MCP URL, complete OAuth, install the plugin and select it in a new chat. The tools must be available in your AI client before it can run a command. Account sign-in alone does not bring a device online. Custom MCP setup →

02 · LOCAL SESSION / AGENT

This device comes online.

Start the supported Golden runtime on the computer you want to use. That live runtime appears to the AI as connected-device and keeps the real OS permission boundary.

03 · ASK FOR THE RESULT

Describe the task normally.

Your AI calls Golden tools, the authorized action runs on the connected machine, and the real result returns to the conversation for verification or the next step.

CURRENT INSTALLATION PATH

No pip package. No Docker onboarding. Use only the current Golden runtime for your platform.

Windows · Session ModeConnect → PowerShell command → browser verification → connected-device

No Node.js and no Windows service. The foreground session stays available while its terminal remains open.

macOS · Session ModeConnect → Terminal command → browser verification → connected-device

No Node.js and no LaunchAgent in foreground mode. Close the terminal or press Ctrl+C to disconnect that session.

Linux · Persistent AgentNode.js 22+ → issued connection code → official Agent installer → connected-device

Linux currently uses the separate persistent user-service path. It is not the macOS foreground Session Mode script.

The exact commands and current platform limitations live in Connections → Installation paths. Do not copy old bootstrap commands from screenshots or previous chats.
SECURITY & DATA FLOW

Know where the action runs and what comes back.

The useful boundary is concrete: the AI reasons in its client, Golden transports authorized tool calls, and the local Session / Agent executes inside the real user and service permissions of the connected environment.

YOUR AIChatGPT / MCP clientReasons, requests tools and receives returned results.
GOLDENAuthorization + routingPublic production transport uses HTTPS and routes the customer tool request.
LOCAL RUNTIMESession / AgentReceives the call for the live connected-device.
REAL ENVIRONMENTComputer / serverOS, files, processes, SSH profiles, CLIs and services keep their own authority.
Where execution happens

Customer commands execute on the connected runtime. An offline customer runtime fails closed; it does not silently fall back to Golden infrastructure.

What reaches the AI

Tool results explicitly returned by the connected device travel back through Golden to the AI. If a command prints file contents or a secret, that returned output can enter the AI conversation.

Permissions stay real

The local OS user, SSH account, authenticated CLI or service identity remains the authority. Golden does not silently sudo, switch users or bypass a denied boundary.

Credentials & secrets

Prefer existing local SSH config, credential stores, authenticated CLIs, environment references or protected files. Golden Secrets / Secure Input is still in development.

Current account activity stores bounded operation metadata such as tool, outcome and timing — not a persistent copy of command arguments, stdout/stderr or project files. Returned tool output can still be visible to your AI client. Permissions → · Audit & Logging → · Golden Secrets →
YOUR FIRST SAFE TASK

Start read-only. Learn the machine first.

After connected-device comes online, start with a request that observes the environment without changing it. You get immediate proof that the connection works and learn what the AI can actually see.

READ ONLY · STORAGECheck how much free disk space is available on connected-device. Do not change anything.
READ ONLY · SYSTEMShow me the basic system information and hardware details for connected-device. Do not change anything.
READ ONLY · SERVICESCheck which services are currently running on connected-device. Do not start or stop anything.
READ ONLY · DOCKERCheck Docker status and summarize what is running. Do not start, stop or remove anything.
Once you understand the environment, move to state-changing work with an explicit boundary: inspect → explain → confirm → act → verify. More starter prompts are in Connections → Useful first prompts.
SSH · REMOTE ACCESS · GOLDEN

SSH gives you access. Golden gives your AI access.

Golden Terminal gives the AI you already use controlled access to your computers, servers, files and infrastructure. It works with SSH, credentials and local tools you trust, without making you transport commands and results by hand.

Manual remote workflow

You become the transport layer.

Your AI→You→SSH / terminal→You→Your AI

The AI suggests. You copy the command, run it, decide what output to copy back and repeat the loop.

Golden workflow

Ask for the result, then verify it.

You→Your AI↔Golden↔connected-device

Existing SSH profiles, authenticated CLIs and service credentials can remain part of the environment. Golden lets the AI use the authorized path directly.

Example flows · illustrative, not live activity
REAL WORK PATTERN

Ask for the outcome.
Golden handles the loop.

These flows illustrate the interaction pattern. Golden never claims an action happened unless the connected environment actually reports it.

AI + GOLDEN TERMINALEXAMPLE FLOW
YouMy Wi-Fi is unstable. Audit the router and improve reliability without rebooting it or changing my admin password.
CHECKEDRouter 192.168.1.1 is stable. The drops start at DNS: this Mac is still using an old DHCP lease and an unreachable DNS server.
ACTIONRenewed DHCP and removed only the stale DNS entry. Router, SSID and Wi-Fi password were left unchanged.
VERIFIED50 pings: 0% loss. DNS: 10/10 lookups. The connection stayed stable through the re-test.
wifidnsdhcpnetwork
Illustrative interaction only · actual actions depend on the connected environment and permissions. MikroTik RouterOS guide. Related real work: router diagnostics and Lightroom recovery.
CAPABILITIES

Real tools. Real environment.

Once the value and boundaries are clear, the capability list becomes simple: Golden exposes the practical surfaces your AI needs to work instead of merely suggesting commands.

>_

Shell

Run commands in the active local user context.

▣

Files

Read, write and patch project files precisely.

◎

Processes

Start work, inspect output and follow process state.

⎇

Git & tests

Use repositories, builds, tests and installed CLI tools.

⬢

Docker

Inspect containers, services and deployment state.

↔

Network

Diagnose reachable infrastructure with the tools already available.

◉

Logs & status

Read evidence before changing the system and verify after.

AI

Your AI client

Golden stays the execution layer. The reasoning remains in your compatible AI.

CASES · REAL WORKFLOWS

Proof before promises.

Every published case is available here. Evidence labels distinguish live-verified results from user-reported workflows.

LIVE CHECK · LOCAL + VPS · READ-ONLY

Checking servers that are online but have failed units

Two live Linux environments had low load and healthy root-disk headroom, yet both showed degraded systemd state. Golden returned real evidence without changing their configuration.

RESULT · two systems audited, follow-up required →
OWNER-REPORTED · ROUTER · SPEED TESTS

Improving a home router and documenting ISP speed discrepancy

Wired tests showed about 45–49 Mbps on a 100 Mbps plan. The owner reports faster Wi-Fi after diagnosing weak signal and disabling unused services.

RESULT · improved network reported; speed gap measured →
OWNER-REPORTED · LIGHTROOM · SOFTWARE REPAIR

Restoring Lightroom after repeated application crashes

Crash logs showed repeated failures; GPU isolation and catalog checks did not help. A newer Lightroom version restored the workflow according to the owner.

RESULT · working after version upgrade reported →
USER-REPORTED · GITHUB · VPS

Deploying a GitHub project with one AI request

A user named a GitHub-hosted project in the AI conversation and asked to install it on an existing server without manually shuttling commands between chat and SSH.

RESULT · one-request deployment reported →
HOME NETWORK · VPN · VERIFIED

Reaching home devices from the office

An existing Linux VPN gateway made two home devices reachable from an office Mac without adding another VPN client to that Mac.

RESULT · 2 device responses verified →
WINDOWS · GPU · LIVE VERIFIED

Restoring broken GPU telemetry

Golden isolated a mixed AMD driver stack, repaired the minimal layer and verified temperature, load, clocks and fan telemetry under stress.

RESULT · telemetry restored →
LINUX · PRODUCTION · VERIFIED

Migrating a production server safely

A live migration kept inventory, TLS, DNS, authentication, rollback and post-cutover verification in one evidence-backed workflow.

RESULT · production verified →
GOLDEN DROP · AI FILE DELIVERY

One connection. Terminal acts. Golden Drop delivers.

Golden Terminal and Golden Drop solve two adjacent execution gaps through the same Golden connection.

GOLDEN TERMINAL

Work with computers and servers.

Give your compatible AI controlled access to shell, files, processes and the tools already available on the connected machine.

HOW CONNECTIONS WORK →
GOLDEN DROP

Deliver AI-created files.

When the AI already has a file, Golden Drop gives it a temporary human-download URL without requiring a separate Drop MCP connection.

OPEN GOLDEN DROP →
KNOWLEDGE

Learn the problem. See the proof. Use the product.

Articles capture broad real-world problems. Cases prove outcomes. Help explains the product boundary and the next practical step.

FROM ANSWER TO ACTION

Your AI already knows the command. Stop carrying it.

Connect Golden and keep working in the AI you already use.