Terminal Use
Ranked 2 of 5 agent hosting services by recommenders
Managed cloud service for filesystem-based agents, handling chat history, session recovery and streaming. Critics say its filesystem and coding-agent assumptions may not fit their use case.
Managed cloud service for filesystem-based agents, handling chat history, session recovery and streaming. Critics say its filesystem and coding-agent assumptions may not fit their use case.
12 people gave an opinion
- recommend it
- 10
- criticize it
- 2
- approval share
- 83%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 10 people recommend itNeeds 10 or more, met.
- 5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Filesystem as core, decoupled primitive
“the decoupled filesystem model makes a lot of sense for long-running agents”
Comment from 10 Mar 2026 in “Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents” “The filesystem-as-first-class-primitive is the right abstraction.”
Comment from 9 Mar 2026 in “Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents” “The filesystem-as-first-class-primitive approach is interesting.”
Comment from 10 Mar 2026 in “Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents” - Comment from 10 Mar 2026 in “Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents”
- Comment from 10 Mar 2026 in “Show HN: Terminal Use (YC W26) – Vercel for filesystem-based agents”
Other agent hosting services people recommend
The four most recommended other agent hosting services, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Klaus | 11 | 6 | 65% | 3 | — | — |
| Terminal UseThis page | 10 | 2 | 83% | 2 | — | — |
| Amazon Bedrock AgentCore | 9 | 1 | 90% | 3 | — | — |
| Kimi Claw | 8 | 5 | 62% | 1 | — | — |
| agent37 Managed OpenClaw hosting | 6 | 1 | 86% | 1 | — | — |
What people said
All 12 comments that mention it, newest first. Each links to the original comment.
“It allows agents to operate fully fledged TUI applications including multiple windows, mouse control, etc.”
“The decoupled filesystem approach makes a ton of sense.”
“it's kind of like a managed cloud services that does agent chat history, session recovery, streaming + a CLI”
“the decoupled storage model is the right primitive”
“The filesystem-as-first-class-primitive approach is interesting.”
“the decoupled filesystem model makes a lot of sense for long-running agents”
“The version pinning approach for existing tasks is a pattern I've found really useful in practice.”
“It’s been a joy to work on.”
“I have a hard time seeing the value in another paid vendor for this”
“We're like langgraph, but for agents that works in a sandbox and needs access to a filesystem to do work.”
“The filesystem-as-first-class-primitive is the right abstraction.”
“the assumptions that Terminal Use is making (about using the file system and coding agent support) would not work for our use case”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.