<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Clusto</title>
    <description>The latest articles on DEV Community by Clusto (@clusto).</description>
    <link>https://dev.to/clusto</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4152467%2F3cd0a777-fef5-4c5a-94fd-50c1786159ab.png</url>
      <title>DEV Community: Clusto</title>
      <link>https://dev.to/clusto</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/clusto"/>
    <language>en</language>
    <item>
      <title>Run your AI coding agents on every machine you own, without opening a port</title>
      <dc:creator>Clusto</dc:creator>
      <pubDate>Tue, 13 Oct 2026 09:09:25 +0000</pubDate>
      <link>https://dev.to/clusto/run-your-ai-coding-agents-on-every-machine-you-own-without-opening-a-port-1pdp</link>
      <guid>https://dev.to/clusto/run-your-ai-coding-agents-on-every-machine-you-own-without-opening-a-port-1pdp</guid>
      <description>&lt;p&gt;Most of us have more than one machine that could run an AI coding agent. A desktop with the big GPU, a homelab box that is always on, a work laptop that holds one repo nobody else has. The agent ends up running wherever you happened to open the terminal, and the session is stuck there: close the lid and it stops, walk to another room and you cannot see it.&lt;/p&gt;

&lt;p&gt;Disclosure: I am on the Clusto team, and this post shows how Clusto handles several machines. The idea behind it (run the agent next to the code, keep the session where it runs, reach it from any device) works with plain SSH and tmux too, just with more glue.&lt;/p&gt;

&lt;h2&gt;
  
  
  One daemon per machine, one mesh
&lt;/h2&gt;

&lt;p&gt;Clusto puts a small daemon, &lt;code&gt;clustod&lt;/code&gt;, on every machine you want to run agents on. On Linux it is one line plus a short wizard:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://dl.clusto.app/install.sh | sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then you join the machines into a cluster from the app: &lt;strong&gt;Cluster &amp;gt; Adopt Node&lt;/strong&gt;, paste a pairing code you generated on the new node, done. No config files to copy, and the node you adopt from checks the new node's identity before it sends anything.&lt;/p&gt;

&lt;p&gt;The cluster is leaderless. Every node applies its own changes immediately and gossips them to its peers, so there is no election and nothing breaks when a node is off. Up to about five nodes form a full mesh. When a machine comes back, the nodes exchange snapshots and catch up.&lt;/p&gt;

&lt;p&gt;What you get in the app is one view of every machine: a card per node with live CPU, memory, swap and network, refreshed about every 10 seconds, and the sessions running on each.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start the agent where the code is
&lt;/h2&gt;

&lt;p&gt;When you open a new chat or terminal session you pick the node it runs on. The New chat dialog has a &lt;strong&gt;Node&lt;/strong&gt; picker, and you can set a default node for every new chat. Claude Code, Codex, OpenCode and OpenRouter models are all available from the same dialog, as long as the CLI is installed on that node.&lt;/p&gt;

&lt;p&gt;The process runs on that machine. Clusto does not migrate processes between nodes, and that is deliberate: the agent needs the repo, the toolchain and the credentials of the machine it runs on. What moves is you. Every node serves the same session list, so you can open the desktop app, the Android app, the web app or the CLI and attach to the session on whichever node owns it. The terminal keeps its scrollback, a chat keeps its transcript and any pending permission prompt.&lt;/p&gt;

&lt;p&gt;If a node goes offline, its sessions show as unreachable instead of disappearing, and come back when the node does.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reaching machines you cannot reach
&lt;/h2&gt;

&lt;p&gt;The awkward part of a multi-machine setup is the network. The homelab is behind your home router, the work laptop is behind a corporate NAT, and the phone is on mobile data. The usual answers are port forwarding, a VPN, or Tailscale on every device.&lt;/p&gt;

&lt;p&gt;Clusto Tunnel is the paid answer to that (it needs a Pro license). Turn it on once for the whole cluster in &lt;strong&gt;Settings &amp;gt; Cluster&lt;/strong&gt;. Desktop and mobile apps then connect to nodes peer to peer over QUIC with hole punching, end-to-end encrypted, and a relay only helps set the connection up. The web app cannot hole-punch from a browser, so it falls back to a relay.&lt;/p&gt;

&lt;p&gt;The tunnel also carries the cluster mesh itself, so a laptop that leaves your network stays a full member of the cluster. Only the machine being dialed needs the tunnel enabled.&lt;/p&gt;

&lt;p&gt;One thing it does not change: the tunnel adds reachability, not access. Every connection still authenticates with the node's own token, exactly like a direct connection.&lt;/p&gt;

&lt;p&gt;If you already run Tailscale or WireGuard, you do not need the tunnel at all. Clustering and remote sessions work on the free Personal plan over any network that can reach the nodes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this looks like day to day
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A long refactor runs on the always-on box overnight. In the morning you check it from your phone and answer the permission prompt it stopped on.&lt;/li&gt;
&lt;li&gt;A quick fix in the work repo starts on the laptop, because that is where the repo and its credentials live.&lt;/li&gt;
&lt;li&gt;The cluster view shows which machine is busy before you start another agent on it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A 26-second walkthrough of the whole flow, recorded from the real app: &lt;a href="https://mastodon.social/@clusto/117432805503724417" rel="noopener noreferrer"&gt;https://mastodon.social/@clusto/117432805503724417&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The free Personal plan covers one user and three devices, including clustering. More at &lt;a href="https://clusto.app/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=agents-across-machines" rel="noopener noreferrer"&gt;clusto.app&lt;/a&gt;, and the details are in the &lt;a href="https://clusto.app/docs/clustering" rel="noopener noreferrer"&gt;clustering docs&lt;/a&gt; and the &lt;a href="https://clusto.app/docs/clusto-tunnel" rel="noopener noreferrer"&gt;Clusto Tunnel docs&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>ai</category>
      <category>devops</category>
      <category>selfhosted</category>
    </item>
    <item>
      <title>Zero-token cron jobs for the chores around your AI coding agents</title>
      <dc:creator>Clusto</dc:creator>
      <pubDate>Fri, 02 Oct 2026 09:44:07 +0000</pubDate>
      <link>https://dev.to/clusto/zero-token-cron-jobs-for-the-chores-around-your-ai-coding-agents-29j8</link>
      <guid>https://dev.to/clusto/zero-token-cron-jobs-for-the-chores-around-your-ai-coding-agents-29j8</guid>
      <description>&lt;p&gt;Not every job you hand an AI coding agent needs the model. A lot of the daily chores around a project are plain scripts: pull some numbers, check that a site answers, run the test suite, write a summary. If you run those through an agent, you pay tokens for work a shell can do for free. If you run them through system cron, the output disappears into a mail spool nobody reads.&lt;/p&gt;

&lt;p&gt;Disclosure: I am on the Clusto team, and this post shows how we run our own chores with Clusto's scheduled tasks. The general idea (script the boring part, save the model for judgment, put every result somewhere you will actually see it) works with any setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pattern
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write the chore as a script that exits 0 on success and non-zero on failure.&lt;/li&gt;
&lt;li&gt;Run it on a schedule on a machine that stays on.&lt;/li&gt;
&lt;li&gt;Have it post a short result to one feed you check from your phone.&lt;/li&gt;
&lt;li&gt;Call a model only for the steps that need judgment, such as "which topic should we write about next", and keep that call in the same schedule.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A real example: our daily marketing stats
&lt;/h2&gt;

&lt;p&gt;Every morning at 08:30 Prague time, a task on one of our servers runs a Node script. It snapshots the reactions and comments on our posts through public APIs, checks follower counts, checks that the website and release manifests respond, and writes a markdown summary. Then the shell posts that summary to the Clusto Reports feed. No LLM is involved, so the run costs zero tokens.&lt;/p&gt;

&lt;p&gt;The whole setup is one command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;clusto task new &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--name&lt;/span&gt; marketing-daily-stats &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--schedule&lt;/span&gt; &lt;span class="s2"&gt;"cron:0_30_6_*_*_*"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--dir&lt;/span&gt; /srv/project &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--cmd&lt;/span&gt; &lt;span class="s1"&gt;'node daily-stats.mjs --out /tmp/daily &amp;amp;&amp;amp; clusto report post --title "Marketing stats $(date +%F)" --body-file /tmp/daily/body.md --level "$(cat /tmp/daily/level.txt)"'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A few details that matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cron expressions have six fields, seconds first, and are evaluated in UTC. &lt;code&gt;0 30 6 * * *&lt;/code&gt; is 06:30 UTC. On the command line, underscores stand in for spaces.&lt;/li&gt;
&lt;li&gt;The command runs through &lt;code&gt;sh -c&lt;/code&gt; on Linux and &lt;code&gt;cmd /C&lt;/code&gt; on Windows, so pipes, &lt;code&gt;&amp;amp;&amp;amp;&lt;/code&gt; and &lt;code&gt;$(...)&lt;/code&gt; work.&lt;/li&gt;
&lt;li&gt;Inside a run, &lt;code&gt;clusto report post&lt;/code&gt; links the report to the task and the run on its own. No IDs to pass around.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where the results go
&lt;/h2&gt;

&lt;p&gt;The Reports feed collects what scripts and agents post: a title, a level (Info, Success, Warning, Error), a markdown body, and optional attachments such as a chart or a CSV. It has an unread badge, search, filters, and grouping by project, task or day. In a cluster, the feed merges reports from every node, so you read one list instead of logging into each machine.&lt;/p&gt;

&lt;p&gt;The part I like most: when a scheduled run fails or times out and no retry is left, the daemon posts an Error report by itself, with the exit code and the tail of the output. A broken automation shows up as a red card the next time you open the app on your phone, instead of a silent exit code in a log.&lt;/p&gt;

&lt;h2&gt;
  
  
  When you do want the model
&lt;/h2&gt;

&lt;p&gt;A task is just a command line, so a headless agent run is a task too:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude &lt;span class="nt"&gt;-p&lt;/span&gt; &lt;span class="s2"&gt;"Read today's report and suggest one topic we have not covered yet"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Clusto does not treat that differently from &lt;code&gt;./backup.sh&lt;/code&gt;. You get the same schedule, history and reports. Split the work so the expensive call only does the thinking: the script gathers data for free, the model reads a short summary.&lt;/p&gt;

&lt;h2&gt;
  
  
  Other things the scheduler handles
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;History: each task keeps its last 50 runs with status, duration, exit code and a cleaned text snapshot of the output (last 64 KB).&lt;/li&gt;
&lt;li&gt;Timeout, retries with a delay between attempts, and extra environment variables per task, set in the app's task dialog.&lt;/li&gt;
&lt;li&gt;Optional notifications on success or failure.&lt;/li&gt;
&lt;li&gt;In a cluster, you pick which node runs a task, and you can move a task with its history to another node later.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Limits to know
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Scheduling lives inside the Clusto daemon, not system cron. The daemon must be running, and a missed slot runs once when it comes back, not once per missed slot.&lt;/li&gt;
&lt;li&gt;The scheduler checks every 100 seconds, so a cron task can start up to about 100 seconds late. Use Run now when timing matters.&lt;/li&gt;
&lt;li&gt;Tasks belong to one node and are not replicated across the cluster.&lt;/li&gt;
&lt;li&gt;The command line is run as-is. Do not paste untrusted input into it.&lt;/li&gt;
&lt;li&gt;Clusto needs a license. The Personal plan is free for one user on up to 3 devices.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full reference: &lt;a href="https://clusto.app/docs/tasks?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=scheduled-tasks" rel="noopener noreferrer"&gt;scheduled tasks&lt;/a&gt; and &lt;a href="https://clusto.app/docs/reports?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=scheduled-tasks" rel="noopener noreferrer"&gt;reports&lt;/a&gt;. Apps for Windows, Linux, Android and the web are on the &lt;a href="https://clusto.app/download?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=scheduled-tasks" rel="noopener noreferrer"&gt;download page&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Persistent AI coding agents: how Herdr, Warp, Conductor, cmux, Cursor and Clusto differ</title>
      <dc:creator>Clusto</dc:creator>
      <pubDate>Wed, 30 Sep 2026 14:19:14 +0000</pubDate>
      <link>https://dev.to/clusto/persistent-ai-coding-agents-how-herdr-warp-conductor-cmux-cursor-and-clusto-differ-2b55</link>
      <guid>https://dev.to/clusto/persistent-ai-coding-agents-how-herdr-warp-conductor-cmux-cursor-and-clusto-differ-2b55</guid>
      <description>&lt;p&gt;If you run AI coding agents for hours at a time, the question is where the work runs and how you get back to it. Several tools cover this now, with different answers. Here is a short map. Disclosure: I am on the Clusto team, so weigh this accordingly. The summaries follow each product's own documentation, and we last reviewed them on September 29, 2026. Features and plans change, so check the linked sources.&lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Main workflow&lt;/th&gt;
&lt;th&gt;Where work runs&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Clusto&lt;/td&gt;
&lt;td&gt;Persistent terminals, structured chats, managed agent teams&lt;/td&gt;
&lt;td&gt;Your own daemon hosts, optional clustering&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Herdr&lt;/td&gt;
&lt;td&gt;Agent-aware terminal workspaces with persistent sessions&lt;/td&gt;
&lt;td&gt;Local and remote servers over SSH&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Warp&lt;/td&gt;
&lt;td&gt;Terminal with integrated code tools and agent automation&lt;/td&gt;
&lt;td&gt;Local terminal, hosted workers, Enterprise self-hosted runners&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Conductor&lt;/td&gt;
&lt;td&gt;Parallel agents in isolated workspaces with review and merge&lt;/td&gt;
&lt;td&gt;Local workspaces and cloud sandboxes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;cmux&lt;/td&gt;
&lt;td&gt;Native macOS terminal workspaces with agent notifications&lt;/td&gt;
&lt;td&gt;Local terminals and remote SSH workspaces&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cursor&lt;/td&gt;
&lt;td&gt;AI editor, coding agents, repository automation&lt;/td&gt;
&lt;td&gt;Local, cloud agents, self-hosted machines&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  When each one fits
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Herdr&lt;/strong&gt; if you want to stay in a terminal. It keeps agent terminals on a background server, shows which agents are working or need input, and offers CLI and socket automation across machines over SSH.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Warp&lt;/strong&gt; if you want a richer terminal with a code editor (language server support, project navigation, Vim keybindings) or an automation platform for your team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Conductor&lt;/strong&gt; if your workflow is parallel repository tasks that end in review and merge, especially with managed cloud sandboxes. It runs Claude Code, Codex, Cursor, and OpenCode.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;cmux&lt;/strong&gt; if you are on a Mac and want agent-aware panes, notifications, and an embedded browser. It supports SSH workspaces and reconnecting to persistent remote sessions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cursor&lt;/strong&gt; if you want editing and delegated development inside the Cursor ecosystem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Clusto&lt;/strong&gt; if you want agents and ordinary shells to live on your own workstations or servers, with desktop, Android, browser, and CLI clients, plus structured chats and managed teams. Its editor is for remote inspection and focused changes, not a full editing environment, and its nodes are machines you provision, so it does not give you a fresh hosted sandbox per task.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose
&lt;/h2&gt;

&lt;p&gt;Try the same workflow in two of them: start an agent on a server, disconnect, reconnect from another device, and respond to an agent that needs input. Persistent remote agents are a shared capability, so the choice mostly comes down to the interface you prefer and where you want the work to run.&lt;/p&gt;

&lt;p&gt;Full comparison with sources: &lt;a href="https://clusto.app/docs/clusto-vs-warp" rel="noopener noreferrer"&gt;Clusto compared with other coding tools&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>productivity</category>
      <category>tooling</category>
    </item>
    <item>
      <title>Keep Claude Code running on your own server and pick it up from your phone</title>
      <dc:creator>Clusto</dc:creator>
      <pubDate>Wed, 30 Sep 2026 14:17:53 +0000</pubDate>
      <link>https://dev.to/clusto/keep-claude-code-running-on-your-own-server-and-pick-it-up-from-your-phone-308c</link>
      <guid>https://dev.to/clusto/keep-claude-code-running-on-your-own-server-and-pick-it-up-from-your-phone-308c</guid>
      <description>&lt;p&gt;Your AI coding agent should not die when your laptop sleeps. If you start Claude Code or Codex in a terminal on your laptop, the session belongs to that terminal. Close the lid, lose Wi-Fi, or drop an SSH connection and the agent stops with it.&lt;/p&gt;

&lt;p&gt;The fix is simple: run the agent on a machine that stays on, and treat your laptop, phone, and browser as windows into that session. Here is how to set that up with Clusto. Disclosure: I am on the Clusto team, so this is the tool I know best. The pattern itself (a persistent session on a server you control) works with other tools too.&lt;/p&gt;

&lt;h2&gt;
  
  
  The idea
&lt;/h2&gt;

&lt;p&gt;In Clusto, sessions live on a small daemon on your own machine, not in the client. You can close the app, switch devices, reconnect, and pick up the same live session. The daemon manages Claude Code, Codex, Copilot, OpenCode, or a plain terminal the same way, over one WebSocket connection.&lt;/p&gt;

&lt;p&gt;When a connection drops, the client resumes the output stream from where it left off instead of refetching the whole history or clearing the screen.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set up a Linux server
&lt;/h2&gt;

&lt;p&gt;Install the CLI, then run the installer:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://dl.clusto.app/install.sh | sh
clusto &lt;span class="nb"&gt;install&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The script installs the CLI for your x64 or ARM64 platform. &lt;code&gt;clusto install&lt;/code&gt; installs the matching daemon, asks for its connection settings, writes the config, and starts the service.&lt;/p&gt;

&lt;h2&gt;
  
  
  Connect from any device
&lt;/h2&gt;

&lt;p&gt;Get an app from &lt;a href="https://clusto.app/download" rel="noopener noreferrer"&gt;clusto.app/download&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Windows: installer (.exe)&lt;/li&gt;
&lt;li&gt;Linux: .deb, .rpm, AppImage, or tarball&lt;/li&gt;
&lt;li&gt;Android: universal APK&lt;/li&gt;
&lt;li&gt;iPhone, iPad, and macOS: the web app at &lt;a href="https://clusto.app/app" rel="noopener noreferrer"&gt;clusto.app/app&lt;/a&gt;. On iOS, open it in Safari, tap Share, then Add to Home Screen.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Open &lt;strong&gt;Connection&lt;/strong&gt; in the app and add the daemon's host, port, and token. The daemon can be on the same machine or a remote server.&lt;/p&gt;

&lt;p&gt;If your server is not reachable directly, Clusto Tunnel connects apps over an end-to-end encrypted peer-to-peer path, so you do not need Tailscale, a VPN, or port forwarding. The web client falls back to a cloud relay. Your node token is still required either way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start a session and walk away
&lt;/h2&gt;

&lt;p&gt;Start a session with your agent of choice on the server, give it a task, and close the client. Later, open Clusto on your phone or in a browser, attach to the same session, and answer the question the agent has been waiting on.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to know before you try it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Clusto needs a license. The Personal plan is free and covers one user on up to 3 devices. Paid plans are Pro (EUR 6/month) and Team (EUR 15/month).&lt;/li&gt;
&lt;li&gt;The web client needs a live connection to your daemon. There is no offline session mode.&lt;/li&gt;
&lt;li&gt;There is no native macOS app yet. Use the web app.&lt;/li&gt;
&lt;li&gt;iPhone and iPad use the web app, not an App Store download.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Setup details are in the &lt;a href="https://clusto.app/docs/downloads" rel="noopener noreferrer"&gt;docs&lt;/a&gt; and the &lt;a href="https://clusto.app/docs/transport" rel="noopener noreferrer"&gt;transport and resume&lt;/a&gt; page explains how reconnecting works.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>linux</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
