钽TANDIU钽铥
PERSONAL AGENT

Agent runtime survey

Each agent answers the same standard questionnaire inside its own runtime, mostly by running commands. The main table keeps only the indicators that matter for choosing; full answers are under Test evidence below.

Data updated: 2026-10-15 09:43
RUNTIME

At a glance

Colour: green = good for long-running agents, amber = conditional, red = unfavourable. Task–runtime consistency = whether the agent’s self-report matches our own tests.

IndicatorMeta Muse2026-10-15Grok Bot2026-10-15LightVela (Tencent Lighthouse)2026-10-15
Runtime typeQ 1VM (sandbox)VPS (cloud computer)VPS (cloud computer)
Machine persistsQ 15, 30No, VM replaced oftenYes, long-term per user (restarts)Yes, one long-lived VM (up 2+ weeks)
Workspace persistenceQ 13Partly, home directory keptKeptKept
Software persistenceQ 14Partly, only under ~/workspaceKeptKept
GUI / browserQ 10, 11No desktop · browser controlDesktop · browserDesktop on demand · browser control
IP stabilityQ 17, 18, 19, 20Low: datacenter, dynamic, geo driftMedium: datacenter, changes within one rangeHigh: Tencent Cloud datacenter IP, unchanged 2+ weeks
Background workQ 21, 22While the VM lives · platform schedulerUntil restart · platform schedulerYes, 2+ weeks uninterrupted · system cron
Lifecycle awarenessQ 16Can detect VM replacementPartly, via boot timePartly, via uptime and files
Task–runtime consistencyConsistent: VM and dynamic egress match our testsConsistent: VPS, kept files and dynamic egress match our testsPartly: long-lived VM and stable IP match our tests; the agent calls itself a sandbox
User takeoverQ 26NoDesktop takeover in the appLimited: SSH/VNC run but need a tunnel
Fit for long-running agentsPartlyYesYes
EVIDENCE

Test evidence

Open a product to see all 30 answers. Source labels are the basis the agent gave (command output, platform docs, past observation, statement, inference, unknown); items that match our own tests are marked.

Meta MuseAll 30 answers · questionnaire V1.0 · 2026-10-15
#QuestionAnswerSource
Base environment
1Environment typeVM (sandbox)The platform tags the task context vm=standard, a managed VM sandbox.Agent: platform docs matches our test
2Own operating systemYesOwn Linux userspace; can run any command and long-lived processes.Agent: command output
3Operating systemUbuntu 24.04.5 LTS (x86_64)Agent: command output
4CPU2 vCPU, AMD EPYC 9D25Agent: command output
5Memory7.7 GiBAgent: command output
6Disk100 GB home partition (about 98 GB free); /tmp is a 512 MB tmpfsAgent: command output
Permissions & tools
7System privileges (root / administrator)Full (root)Agent: command output
8Install software yourself (apt / pip / npm)YesAnything under ~/workspace persists; system-wide installs disappear when the VM is replaced.Agent: command output
9Run shell commands directlyYesAgent: command output
10Graphical desktopNoHeadless; Xvfb is only for browser automation.Agent: command output
11Launch and control a browserYesDrives Chromium through platform browser tasks; a new browser process per task.Agent: past observation
State persistence
12Browser logins kept across sessionsPartlyKept while the same VM lives; lost when it is replaced.Agent: past observation
13Files kept across sessionsPartlyThe home directory survives VM replacement; /tmp and system directories do not.Agent: past observation
14Installed software kept across sessionsPartlyTools under ~/workspace persist; system-level installs do not.Agent: past observation
15VM may be deleted, rebuilt or replaced by the platformYesPlatform deploys are frequent (often hourly), so the VM can be replaced at any time.Agent: platform docs
16Can it tell when the VM is replacedYesMissing non-home files, a changed machine-id, or a jump in egress IP.Agent: past observation
Network & IP
17Public egress IP static or dynamicDynamicBrowser egress rotates within a proxy pool.Agent: past observation matches our test
18Egress IP same across sessions / restartsNoAgent: past observation matches our test
19Egress IP typeDatacenterSeen as Fastly AS54113 and Cloudflare AS13335; shell and browser use different egress, and the browser one is what sites see.Agent: past observation
20Egress country / region may changeMay changeThe same IP geolocates differently across databases (Virginia / New York / San Francisco / Montreal).Agent: past observation
Long-running capability
21Background processes survive the taskSometimesSurvives while the VM lives; stops when the VM is replaced.Agent: platform docs
22Scheduled jobsVia platform schedulerPlatform-managed cron / hooks, not the system crontab.Agent: platform docs
23Longest run timeUnknownA single task is capped at 86,400 seconds; how long a VM lives is unknown.Agent: unknown
24Paused or reclaimed when idleYesVMs are replaced on platform deploys, regardless of idleness.Agent: platform docs
25Snapshot / resumeNoNo whole-machine snapshot; home files persist and the platform resumes scheduled tasks.Agent: platform docs
Access & services
26User can enter via SSH / RDP / VNCNoNo inbound ports are open.Agent: platform docs
27Outbound internet accessYesSome sites block datacenter IPs.Agent: command output
28Listen on a port reachable from the internetNoNo public IP; only via a reverse tunnel.Agent: platform docs
29Credentials kept long-term across tasksYesCredentials in the Secure Vault persist across tasks and VM replacements.Agent: platform docs
30Who the environment belongs toLong-term per userThe home directory is long-term and per user, but the compute instance underneath gets replaced.Agent: platform docs

The agent’s own summary

  • Environment type: VM (sandbox)
  • Persistence: Medium
  • IP stability: Low
  • Self-awareness: High
  • Fit for long-running agent work: Partly

Home directory and credentials survive VM replacement and platform schedules run long-term, which suits orchestration; but the compute instance is replaced at any time and the egress is a dynamic, geo-drifting datacenter IP, so it does not suit fixed-IP, long-lived process or inbound-service work.

Grok BotAll 30 answers · questionnaire V1.0 · 2026-10-15
#QuestionAnswerSource
Base environment
1Environment typeVPS (cloud computer)A long-lived Linux VM.Agent: command output matches our test
2Own operating systemYesAgent: command output
3Operating systemDebian 13 (trixie)Agent: command output
4CPU8 vCPU, Intel XeonAgent: command output
5Memory15 GiB (about 16 GB)Agent: command output
6Disk125 GB (120 GB free)Agent: command output
Permissions & tools
7System privileges (root / administrator)Full (regular user with passwordless sudo)Agent: command output
8Install software yourself (apt / pip / npm)YesAgent: command output
9Run shell commands directlyYesAgent: command output
10Graphical desktopYesGraphical desktop (X displays :1–:3).Agent: command output
11Launch and control a browserYesChrome is operated by a desktop-control agent rather than scripted directly.Agent: command output
State persistence
12Browser logins kept across sessionsKeptAn X account logged in the previous day was still logged in.Agent: command output
13Files kept across sessionsYesFiles created on the two previous days were still there after a restart.Agent: command output matches our test
14Installed software kept across sessionsYesAgent: statement
15VM may be deleted, rebuilt or replaced by the platformRestarts; deletion or rebuild unknownThe user can update or reset the computer in settings.Agent: platform docs
16Can it tell when the VM is replacedPartlyBy boot time and whether files are still there; the platform does not notify.Agent: command output
Network & IP
17Public egress IP static or dynamicDynamicEgress moved within the same Cloudflare range 104.28.243.x on two days.Agent: command output matches our test
18Egress IP same across sessions / restartsNoAgent: command output matches our test
19Egress IP typeDatacenter (Cloudflare AS13335)Agent: command output
20Egress country / region may changeMay changeSeoul so far; browser egress can be switched to the user's own egress in settings.Agent: command output
Long-running capability
21Background processes survive the taskSometimesSurvives the end of a chat, lost on machine restart.Agent: inference
22Scheduled jobsVia platform schedulerAlready running platform schedules (daily and weekly).Agent: command output
23Longest run time13 minutes per command, can move to background; machine lifetime unknownAgent: platform docs
24Paused or reclaimed when idleUnknownRestarts have been observed.Agent: unknown
25Snapshot / resumePartlyDisk contents survive restarts; no snapshot it can call itself.Agent: command output
Access & services
26User can enter via SSH / RDP / VNCDesktop takeover in the app; SSH unknownDesktop takeover was used to log in to X.Agent: command output
27Outbound internet accessYesAgent: command output
28Listen on a port reachable from the internetUnknownIt can listen on ports; reachability from the internet not verified.Agent: unknown
29Credentials kept long-term across tasksPartlyThe platform has encrypted secret storage, and browser logins persist.Agent: platform docs
30Who the environment belongs toLong-term per userAll of a user's agents share one computer, each with its own desktop.Agent: platform docs

The agent’s own summary

  • Environment type: VPS (cloud computer)
  • Persistence: High
  • IP stability: Medium
  • Self-awareness: Medium
  • Fit for long-running agent work: Yes

A long-lived Debian cloud computer per user (8 cores, 16 GB, 125 GB) with root, a desktop and a browser; files, software and logins survive restarts, and long-running work uses the platform scheduler. Egress is a changing Cloudflare Seoul datacenter IP; restarts and rebuilds are not announced.

LightVela (Tencent Lighthouse)All 30 answers · questionnaire V1.0 · 2026-10-15
#QuestionAnswerSource
Base environment
1Environment typeVM (sandbox)The agent labels itself a sandbox, but describes a single long-lived dedicated VM, which is a VPS by our definition.Agent: command output
2Own operating systemYesAgent: command output
3Operating systemUbuntu 24.04.4 LTSAgent: command output
4CPU2 vCPU, AMD EPYC 9K84Agent: command output
5Memory7.4 GiBAgent: command output
6Disk50 GB root (28 GB free)Agent: command output
Permissions & tools
7System privileges (root / administrator)Full (regular user with passwordless sudo)Agent: command output
8Install software yourself (apt / pip / npm)YesSystem Python needs a venv/uv for packages.Agent: command output
9Run shell commands directlyYesAgent: command output
10Graphical desktopYes (on demand)XFCE + noVNC installed but off by default; started manually.Agent: command output
11Launch and control a browserYesVia the built-in Hermes browser tool.Agent: platform docs
State persistence
12Browser logins kept across sessionsUnknownThe browser is managed by the tool layer; not verified.Agent: unknown
13Files kept across sessionsYesThe environment has been up for 2+ weeks and earlier files are still there.Agent: command output
14Installed software kept across sessionsYesSelf-installed software (e.g. Tailscale, XFCE) is still there.Agent: command output
15VM may be deleted, rebuilt or replaced by the platformUnknownLong-lived with no reclaim seen, but no platform commitment.Agent: unknown
16Can it tell when the VM is replacedPartlyMissing files, a reset uptime or a changed IP; no notification.Agent: inference
Network & IP
17Public egress IP static or dynamicUnknown (likely static)Egress 161.120.186.x, unchanged for 2+ weeks, no platform commitment.Agent: command output matches our test
18Egress IP same across sessions / restartsUnknownLikely the same (a long-lived VM, not per-task).Agent: unknown
19Egress IP typeDatacenter (Tencent Cloud)Agent: command output
20Egress country / region may changeFixedUnless the VM is rebuilt.Agent: inference
Long-running capability
21Background processes survive the taskYesLong-lived processes such as x11vnc and hermes have run for 2+ weeks.Agent: command output
22Scheduled jobsYesSystem cron works, and Hermes has its own scheduler.Agent: command output
23Longest run timeUnknownRunning continuously for 2 weeks 1 day so far.Agent: command output
24Paused or reclaimed when idleUnknownNo pause or reclaim seen.Agent: unknown
25Snapshot / resumeUnknownPlatform snapshots unknown; the desktop must be restarted by hand after a reboot.Agent: command output
Access & services
26User can enter via SSH / RDP / VNCServices run, but inbound is blockedsshd and VNC work, but the cloud firewall blocks inbound traffic, so access needs a tunnel.Agent: command output
27Outbound internet accessLimited (mostly works)A few domains do not resolve.Agent: command output
28Listen on a port reachable from the internetLimited (effectively no)It can listen, but the internet cannot reach it except through a tunnel.Agent: command output
29Credentials kept long-term across tasksYesHermes has an encrypted vault with 1Password/Bitwarden integration.Agent: platform docs
30Who the environment belongs toLong-term per userA single long-lived VM that stays across sessions.Agent: platform docs matches our test

The agent’s own summary

  • Environment type: VM (sandbox)
  • Persistence: High
  • IP stability: High
  • Self-awareness: High
  • Fit for long-running agent work: Yes

A dedicated Ubuntu 24.04 VM with root, installs, cron and background processes alive for 2+ weeks; files and software persist and egress is a stable Tencent Cloud datacenter IP. Downsides: inbound traffic is fully blocked by the cloud firewall (tunnel needed), and the VM lifecycle and reclaim policy are unknown.

The questionnaire: Agent runtime standard questionnaire V1.0 →