Before the run
Check before adding more.
Guard reads the computer’s resource pressure before starting a heavy test. When capacity is tight, the new run waits instead of adding to the load.
Resource-aware admissionBUILT FOR AGENT WORKLOADS
Built for the way AI agents use compute.
Agents build, test and launch processes. Often at the same time. TermSquad Guard helps keep heavy test runs from overwhelming the computer they all share.
- For heavy test suites
- Enabled by default
- Resource-aware starts
Your TermSquad ComputerA shared home for your agent workloads
Unit tests
Browser tests
Integration tests
TermSquad GuardCheck capacity before starting
MemoryCPU pressureDisk I/O
Capacity availableRun with limitsTest + child processes
Under pressureWait for resourcesCheck again before starting
Headroom for core services
What is TermSquad Guard?
TermSquad Guard is workload protection for heavy test suites on your TermSquad Computer. It checks resource pressure before starting a guarded run and limits its memory use to leave headroom for essential services.
Why agent workloads need guardrails
More agents.
The same computer.
One agent can start a test suite while another installs dependencies or builds your app. They share the same CPU and memory. Checking capacity before adding another heavy test helps keep that burst of work manageable.
During the run
Give tests a boundary.
Guarded tests and their child processes share memory and swap limits. A timeout stops a run that goes on too long, and cleanup removes its remaining processes.
Memory limits + timeoutsAround the run
Leave room for the essentials.
Guard reserves memory headroom and gives test workloads lower resource priority. Core platform protections help keep the runtime and connection services available.
Headroom for core servicesBuilt for heavy test suites. Guard’s checks and per-run limits apply when tests run through Guard. Commands launched directly do not receive those same limits.
How TermSquad Guard works
A little patience.
A healthier workspace.
With Guard enabled, the TermSquad Skill guides your agents to use it for heavy tests. You can also run a suite through Guard yourself.
- 01
Check the computer.
Run a heavy test suite through TermSquad Guard. It checks available memory, CPU and disk I/O pressure, swap activity and recent memory exhaustion before starting.
- 02
Wait when it needs a breather.
If the computer is under pressure, the new test waits. Guard checks again and lets it start once resources have recovered and stabilized.
- 03
Run within limits.
The test and its child processes run within memory and swap limits. Guard enforces a timeout and cleans up the workload when it ends.
agent@termsquad
# A heavy test suite, through Guard
termsquad guard test -- pnpm testWaiting for machine resources
before running tests…
# Starts once resources recover
Test runs within memory limits
Waiting is part of the protection.
Guard rechecks resources automatically. After memory exhaustion, it allows a recovery window before admitting more work.
Running a suite yourself?
From the agent user on your TermSquad Computer, replace pnpm test with your test command. The default run timeout is one hour; a longer suite can use:
termsquad guard test --timeout 90m -- pnpm testWhile Guard asks you to wait, let it wait. Starting the same suite directly bypasses its checks.
Know your computer’s capacity
See the pressure.
Know your next move.
Open Metrics to see CPU, memory, disk, swap and uptime. Review the last hour, 24 hours or seven days, and inspect service and workload usage when reported.
If memory pressure persists, stop unused processes, reduce parallel work or move to a larger plan. Guard works within the resources you have.
Compare computer plansResource visibilityIn Metrics
- CPU
- See how busy your computer is.
- Memory
- Track RAM usage and capacity.
- Disk
- Know how much storage is left.
- Swap
- See use of the memory safety buffer.
Available readings come from your computer. Missing measurements are marked unavailable.
Frequently asked questions
A clearer view
of the guardrails.
What Guard handles, what you control, and when more resources can help.
Explore the documentationWhat is TermSquad Guard?
TermSquad Guard protects your TermSquad Computer when running heavy test suites. It checks resource pressure before admitting a guarded test, waits when capacity is tight, and applies memory limits and a timeout to the run.
Does Guard automatically protect every command?
Guard’s admission checks and per-run limits apply to tests launched through the Guard command. With Guard enabled, the TermSquad Skill instructs agents to use it for heavy test suites. Commands run directly do not receive those per-run checks and limits. Core platform protections remain active separately.
What happens when several agents run tests at once?
Each guarded test checks machine pressure before starting. When resources are under pressure, new guarded runs wait for recovery. Tests already running stay within their assigned memory limits. The number of runs the computer can support depends on the tests and available resources.
Can Guard stop a running test?
Yes. A guarded test can be stopped if it exceeds its memory limit or timeout. Guard reports the outcome and cleans up its processes. It helps contain resource exhaustion; it does not guarantee that every test completes or that the computer can never run out of memory.
Can I turn TermSquad Guard off?
Yes. Guard is enabled by default and can be turned off in the computer’s settings if you manage workload protection yourself. This changes the agent’s Guard workflow policy. Core TermSquad service protections, swap and resource monitoring stay enabled, and the Guard command remains available.
Which resource metrics can I see?
The Metrics page shows CPU, memory, disk, swap and uptime, with history views for one hour, 24 hours and seven days. Service and workload usage appear when reported by the computer. Missing measurements are shown as unavailable.
Does Guard add resources or upgrade my computer automatically?
No. Guard manages heavy test runs within your computer’s existing capacity. If memory pressure persists, stop unused processes, reduce parallel work or choose a larger plan. Guard does not add CPU or RAM or automatically upgrade your subscription.
A home for ambitious agent work
Give your agents room to work.
And guardrails to work within.
Your cloud computer. Your tools. Workload protection built in.
AI subscriptions and usage are not included.