Instinct: a practical decision dossier
A personal-context assistant described around connected signals and proactive help.
Facts before opinions. Every entry links to its source and distinguishes publication dates from review dates.
A personal-context assistant described around connected signals and proactive help.
A self-managed assistant with a CLI, messaging gateway and inspectable memory files.
A hosted assistant with persistent computer state and plan-dependent access.
An always-on ChatGPT agent with a cloud computer and account-dependent rollout.
A separate Manus personal-agent app emphasizing independent agent identities and collaboration.
A pinned CLI and backup baseline exposed a real prerequisite: OpenClaw 2026.9.6 requires Node 24.16+ on the 24.x line or 26.1+. Package version and running gateway identity must be checked separately. No upgrade was performed.
Review files, commands, permissions and outbound destinations before adding a skill. Keep a reversible install record and verify removal in a new session.
A runnable Node example fetches feeds, removes duplicate URLs and remembers seen items. Live inputs produced 35 unique entries; an unchanged replay produced zero new entries. Agent scheduling remains untested.
Check timezone, execution logs, destination and cleanup with a single harmless event. The current OpenClaw docs use automations; cron remains an alias.
Separate model instructions, tool approvals and operating-system access. Use an allowed read and a denied write to test the effective boundary.
Verify sender access, conversation routing and actual reply delivery separately. Start with a private test chat; gateway registration alone is not a successful integration.
The checked documentation separates profile-local files, staged writes and the frozen session-start snapshot. Verify a correction with a saved record and a fresh-session action. Model behavior remains untested.
A small acceptance procedure separates installation, provider connectivity, tool execution and session persistence. Use harmless local input before adding messaging or schedules.
Use a controlled task and record evidence, completion time, failures and observed cost. Choose for your deployment and workflow constraints rather than a general score.
Real Windows x64 and macOS ARM64 CLI runs restored all five fictional files. Config-only restored the root JSON but omitted its include file. Corrupt archives and occupied targets were refused; gateway recovery was not tested.
Skills expose a directory first and load detailed instructions or references only when needed. The documentation also covers installation and /learn. Skill files remain editable; review their source and execution permissions before using them.
Website review date, not publication date
One gateway can host multiple agents with separate workspaces, state and session history. Bindings route incoming messages. The documentation warns against sharing agentDir, making it useful when separating work and personal assistants.
Website review date, not publication date
The official quickstart covers installation, model providers and troubleshooting. Verify an ordinary conversation first, then connect a messaging gateway and add skills, automation or routing incrementally so configuration problems stay easier to diagnose.
Website review date, not publication date
The official automation index explains persistent jobs, schedules, triggers and delivery to chat channels or webhooks. Start with a reminder or recurring brief, then inspect run history rather than assuming a configured job has succeeded.
Website review date, not publication date
No English summary yet — see the cited source.