Skip to main content
Answers to common questions about Catty.

General

Catty is a platform that runs Claude Code in persistent cloud sessions. It streams the terminal to your local machine, giving you a native experience while the AI runs remotely.Key features:
  • Sessions persist even when you disconnect
  • Run multiple sessions in parallel
  • Automatic workspace upload and sync-back
  • Reconnect from anywhere
AspectCattyLocal Claude Code
PersistenceSessions keep running when you disconnectStops when terminal closes
Parallel sessionsRun multiple sessions simultaneouslyOne session per terminal
LocationReconnect from any machineTied to one machine
File syncAutomatic bidirectionalN/A (already local)
Catty is ideal for:
  • Developers who want sessions that persist across disconnects
  • Anyone who needs to run multiple Claude Code sessions in parallel
  • Users who work from different locations
  • Teams that want automatic file sync between local and remote

Platform Support

Supported:
  • macOS (Intel and Apple Silicon)
  • Linux (x64 and ARM64)
Not yet supported:
  • Windows
Windows support is on the roadmap.
Node.js 18 or later is required to install the CLI via npm.
Not currently. The CLI is distributed via npm. You can use npx @diggerhq/catty without a global install.

Sessions

Yes! You can run multiple sessions in parallel for different projects or tasks. Use catty list to see all your active sessions.
Sessions have a TTL (time-to-live) and will auto-stop after extended inactivity. You can also stop them manually with catty stop.
The cloud machine is destroyed when a session stops. Any files not synced back to your local machine are lost.With sync-back enabled (default), all changes Claude makes are automatically synced to your local directory in real-time, so you won’t lose work.
Yes! Sessions persist until stopped. Disconnect with Ctrl+C and reconnect later with catty connect <label>.

Security & Privacy

Yes. Each session runs in its own isolated cloud machine. Your workspace files exist only on that machine and are deleted when the session ends.
  • Sessions are isolated from each other
  • Only you can access your sessions (via your auth token)
  • No workspace data is persisted after session termination
Locally at ~/.catty/credentials.json with restricted file permissions (0600). Credentials are only sent to the Catty API for authentication.
Your workspace is uploaded to the session machine, which Catty operates. However:
  • Files are only stored on the ephemeral session machine
  • Files are deleted when the session ends
  • Catty doesn’t analyze or store your code beyond the session lifetime
Catty doesn’t log the content of your API calls to Claude.

Billing

Catty offers two plans:
  • Free tier: Limited usage per month
  • Pro: $25/month for higher limits
No. Catty provides Claude API access. You don’t need your own API key.
You can’t create new sessions. Existing sessions continue working. Options:
  1. Wait for monthly reset
  2. Upgrade to Pro
No. Cloud compute costs are included in your plan. You only pay for token usage.

Technical

Sessions run on Debian (node:22-bookworm) with development tools pre-installed:
  • Node.js 22
  • Git
  • Build tools (gcc, make)
  • ripgrep, jq, vim, curl, wget
  • Python (with pip)
  • And more
Claude Code has access to all standard Unix tools.
Yes, within the session. Use apt-get, npm, pip, etc. However, installations don’t persist across sessions.
100 MB. Use .gitignore to exclude large files, or use --no-upload and clone your repo in the session.
Sync-back is one-way (remote to local). If you edit a file locally while Claude edits it remotely, the remote version will overwrite your local changes.Best practice: Don’t edit files locally during an active session. Let Claude do the work, then review when done.

Troubleshooting

Open an issue on GitHub: github.com/diggerhq/catty/issuesInclude:
  • CLI version (catty version)
  • OS and architecture
  • Full error message
  • Steps to reproduce
  • Check Common Issues for solutions
  • Open a GitHub issue for bugs
  • Review this FAQ for general questions