GigAgentWrite the job
In the dashboard, say what needs doing in plain English, pick the one folder it may work in, choose a model and decide when the code expires.
New One-time codes. Live view. Nothing to sign up for.
Get work done on someone else's computer with one command.
Write the job in your dashboard. Send a one-time code. They paste one line into Terminal, and an AI agent does the work on their Mac while you watch live. Nothing to sign up for, no API key for them. One line in Terminal.
macOS today. Codes are single-use, and you can stop the agent from your dashboard at any time.
Maya's MacBookLive
Result
Ready for day one, with one fix: macOS is two versions behind. FileVault is on. 61 GB free.
The gap
Everyone has heard of AI. Most people have never watched one do real work on their own computer.
About half of U.S. adults now use AI chatbots1. But chatting is not the same as an agent that opens a folder and gets something done. Running an agent today still means a terminal, API keys, installs and config, so only a small fraction of people have ever tried one. Most never will.
Agents today
Built for people who live in a terminal
Pick a tool, install it, sign up, generate an API key, paste it in the right place, then write a good prompt. Every step is a place to give up.
- install runtime
- create account
- get API key
- edit config
- write prompt
With GigAgent
The expert sets it up. The person pastes one line.
You, the person who knows what needs doing, write the job and hold the keys. The person at the computer needs nothing but Terminal and a code.
$npx gigagent K7QM-4XPA
1. Pew Research Center, About half of U.S. adults now use AI chatbots, up from a third in 2024 (survey conducted Feb 17–23, 2026). The statement about agents is our own observation, not a survey figure.
How it works
From "can you take a look?" to done, in three steps.
No screen share. No remote desktop. No back and forth.
Send the code
You get a one-time code. Text it, email it, read it over the phone. They open Terminal and run:
npx gigagent K7QM-4XPAGet the result back
The agent does the work and returns a plain-English summary for them and the answer, key findings and changes for you. Then it removes itself from their Mac.
You stay in control the whole time.
- Watch liveEvery command and file the agent touches shows up on your dashboard as it happens.
- Send instructionsSpotted something mid-job? Add an instruction and the agent picks it up.
- Stop anytimeOne click revokes the session. The next model call fails and the agent halts.
Use cases
The jobs you would normally do over someone's shoulder.
Anything you could do by looking around a Mac and tidying or writing something down, a person can now hand to an agent with one line.
New-hire onboarding and laptop readiness
"Check this Mac is ready for day one: OS, updates, disk, FileVault, required apps."
Replace the 45-minute setup call with a checklist the new hire kicks off themselves.
Outcome: a pass/fail readiness report before IT spends a minute on the laptop.
Diagnostics for "why is my Mac slow?"
"Find out why this Mac is slow. Check disk, memory and top processes."
The agent gathers the facts you would ask for over the phone, in the order you would ask.
Outcome: disk, memory and the top offenders, plus a likely cause.
Desktop clean-up and disk space rescue
"Sort the Desktop into folders by type and tell Dad what is taking up space."
Skip the 40-minute call. The agent is instructed to move files rather than delete them, and to log every move so it can be undone.
Outcome: a tidy Desktop, a plain-English guide and an undo log.
Setting up client machines
"Audit this client Mac and list what is installed, what is out of date and what is missing."
Send the same job to every client. Each one runs a single line and you get a comparable report.
Outcome: consistent audits across clients without a site visit.
Student and lab machine checks
"Report free disk space and macOS version on this lab Mac."
Hand a code to whoever is at the machine and collect results without visiting every desk.
Outcome: a fleet snapshot gathered by the people sitting there.
IT help without an IT department
"Check backups, disk space and system updates on the front-desk Mac."
Whoever is the unofficial computer person writes the job; staff only need to paste a line.
Outcome: routine health checks without hiring or a contractor visit.
Info for tickets and asset inventory
"Collect macOS version, FileVault status, serial number and installed apps."
Stop asking "can you go to About This Mac and read me the number?" and get it in one pass.
Outcome: a structured record you can paste straight into a ticket or sheet.
File organisation projects
"Group Downloads into Documents, Images, Installers and Other. Flag duplicates."
Works inside the one folder you choose. Duplicates are flagged and moved aside rather than erased.
Outcome: sorted folders, a list of duplicates and the undo log.
Honest about v0. The agent is instructed to stay inside the folder you chose, not to install software and not to use admin rights. Those are rules it follows, not locks: the commands it runs are not sandboxed, so only hand a code to someone you would trust with that, and watch the live view. It is also not a replacement for a full device-management tool. It runs on macOS only for now, and needs Node.js 22+ on the Mac.
ROI
See what an hour of setup call is really costing you.
Every onboarding call burns two people's time: IT and the new hire. Plug in your numbers and see how much of it comes back.
Estimated time returned each year
417 hours
saved per year
$37,483saved per year
14.4work-weeks returned
hours = (hires × min per hire × people ÷ 60) + (tickets/mo × 12 × min per ticket ÷ 60)
dollars = hours × hourly cost · work-weeks = hours ÷ 40
Example at scale
1,000 hires × 50 min × 2 people = 100,000 minutes ≈ 1,667 hours ≈ 42 work-weeks a year, before counting a single support ticket.
These figures are estimates based on the inputs you enter. They are not guarantees, and real savings depend on how many jobs you hand to GigAgent and how long they take today. Model usage costs are not subtracted; they are typically cents per job.
Results
Results come back to you, structured and ready to use.
No scrolling through a chat log. When the job finishes, the agent returns a structured result: a plain-English summary for the person at the computer, and the answer, key findings and changes for you.
- Summary in plain language for the person at the keyboard.
- Answer and key findings for you, easy to paste into a ticket.
- Changes listed one by one, so nothing is a surprise.
Delivered to email
and Slack
Also on your dashboard
Laptop readiness: Maya's MacBookExample result, session finished in 2m 14s
Done
Summary for Maya
Your laptop is nearly ready. Everything important is set up. One thing is left: a macOS update, which we will schedule for tonight.
Answer
Ready for day one, with one fix needed: macOS is two versions behind.
Key findings
| Check | Result | Status |
|---|---|---|
| macOS | Two versions behind | Update |
| FileVault | On | Pass |
| Free disk | 61 GB of 245 GB | Pass |
| Required apps | 6 of 6 present | Pass |
Changes
- wrote laptop-readiness.md
- moved nothing
Security and trust
Designed to be handed to someone who is not technical.
Some protections are built into the system. Others are rules the agent is instructed to follow, and we keep the two apart so you know which is which.
Built into the system
The AI key never reaches their Mac
The server proxies every model call. The recipient's machine only ever holds a short-lived session token, never your provider key.
Revoke a code, stop the agent
Revoke or stop a session and its next model call is refused. The agent has no model access without the server's say-so.
One-use codes
A single-use code works once. Run it again and it is rejected. You can also set codes to expire on completion or after a set time.
You watch every command live
Every command the agent runs, its output (up to 2,000 characters each) and the files it opens stream to your dashboard live, with the option to send instructions or stop.
Cleans up after itself
When the helper exits normally, it removes its temporary files from the Mac. A power loss or force-quit can leave them behind.
Rules the agent follows
These are instructions given to the agent, not technical locks. The agent's commands are not sandboxed, so treat them as strong guidance rather than a guarantee.
Works in one folder
You choose the working folder. The agent is instructed to only change things inside it. It may run read-only commands elsewhere to look up information, such as the macOS version or installed apps.
Moves instead of deleting
The agent is instructed not to delete files, empty the Trash or overwrite anything. Anything that has to go is moved aside.
Logs every move for undo
The agent is instructed to write each move to an undo log in the folder, so a clean-up can be reversed.
No sudo, installs or network
The agent is instructed never to use admin rights, install software, or download or upload anything.
FAQ
Questions people ask before they send a code.
What do they need?
A Mac with Node.js 22 or newer, plus Terminal. Node.js is a free installer from nodejs.org, and IT-managed Macs often have it already. If it is missing or too old, GigAgent explains what to do. (If Node.js is not installed at all, macOS just says
command not found: npx.) They do not need an account or an API key.Does it install anything permanently?
No permanent install.
npx fetches the helper on demand, it runs once, and it removes its temporary files when it exits normally. A power loss or force-quit can leave them behind. The agent is also instructed not to install software.What can it see?
It is instructed to work inside the one folder you pick for the job and to change nothing outside it, though it may run read-only commands elsewhere to look up information such as the macOS version or installed apps. Its commands, their output (up to 2,000 characters each) and the files it opens are streamed to you, so you see what it sees. macOS may ask the person to allow Terminal to access that folder, which is normal.
What if it goes wrong?
You can stop it from your dashboard at any time, and the person can press Ctrl+C. The agent is instructed to move files rather than delete them and to write each move to an undo log in the folder, but that is a rule it follows, not a technical lock. Revoking the code does cut off its access to the model immediately.
Which models does it use?
Models run through Vercel AI Gateway, so you can pick from Claude, GPT, DeepSeek and others per job. The model call goes through our server, never directly from the recipient's Mac.
Who sees the commands and files?
You do, as the operator: the dashboard shows each command, its output (up to 2,000 characters) and the files the agent opens. That same content is also sent to the model provider, through Vercel AI Gateway, so the model can do the job. Do not point it at a folder whose contents you would not want you or the provider to see.
Does it work on Windows?
Not yet. GigAgent is macOS only today. Windows and Linux are not supported in this version.
What does it cost?
The cost is model usage, and for a typical job like a folder clean-up or a system check that is usually cents per job. The exact amount depends on the model you choose and how long the job runs.
Does the person need an account or API key?
No. They need the code, Terminal and Node.js 22 or newer. Everything else, including the model access, is handled on your side.
Stop driving over. Send a code.
Write the job, share the code, and watch it get done. Your first one takes about a minute.