Persistent Storage

Levelsio exported diet logs from Claude chat into Claude Code on a VPS, then built Caltrack with Telegram, SSH entry, database memory, and Grok vision food scanning. The case turned failed chat memory into a persistent app.

Creator threads and Anthropic interviews documented Claude Code setups that run on VPS instances, stay reachable from phones, and keep working overnight. The setup matters because coding, deployment, and review can happen inside one persistent environment instead of a local machine session.

levelsio said he now ships directly on production VPSes with Claude Code, backed by 3-2-1 backups and almost no dependencies. The thread ties a vanilla PHP, JS, and SQLite stack to two brief outages in a year, so lower complexity may keep AI-assisted bugs manageable.

Holaboss launched holaOS Beta 0.1 with permanent workspaces, sub-agents, and a dashboard for recurring tasks and review loops. Use it if you want persistent project memory instead of reset-every-run agent chats, though the evidence is mostly launch-thread documentation.

Creators documented running Claude Code on always-on VPS setups with SSH, mosh/tmux, and /resume so sessions survive laptop sleep. It cuts battery drain and lost progress, but image paste and remote file handoffs still feel clunky.

New Hermes Agent and Claude Code playbooks mapped memory, skills, soul, crons, and nightly GitHub sync into repeatable personal-OS setups. The guides push agent workflows into daily content and admin tasks while surfacing security and stale-memory failure modes.

Anthropic introduced dreaming as a research preview in Claude Managed Agents alongside multiagent orchestration, rubric-based self-improvement, and webhook updates. Sub-agents now share a container and filesystem, so teams can coordinate longer-running work and manage memory across sessions.

A Hermes and Kimi hackathon build mapped a local filmmaking pipeline with prompt packets, browser workers, Syncthing handoff, image ranking, and taste memory. It matters because subscription-only tools can be folded into a reusable production loop, but the taste model is still early and creator-specific.

Cross-author demos showed Hermes using self-rewriting skill files, timeboxed subagents, and recurring brief workflows that improved over repeated runs. It matters because creators and vibe-coders can compound agent behavior across sessions, though the evidence still comes from user-run setups rather than a full official product brief.