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
  • Workspaces auto-save to the cloud every 30 seconds
  • GitHub integration for private repos
  • Reconnect from anywhere
AspectCattyLocal Claude Code
PersistenceSessions keep running when you disconnectStops when terminal closes
Cloud backupWorkspace saved every 30s, downloadable anytimeN/A
GitHub accessClaude can clone, push, create PRsDepends on local setup
LocationReconnect from any machineTied to one machine
Catty is ideal for:
  • Developers who want sessions that persist across disconnects
  • Users who need cloud backup of their work
  • Anyone working with private GitHub repositories
  • Teams that work from different locations

​
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

Sessions have a TTL (time-to-live) of 2 hours of inactivity. They can also be stopped manually with catty stop.
Workspaces are automatically saved to the cloud every 30 seconds. When a session stops:
  1. A final save is performed
  2. The cloud machine is terminated
  3. Your files remain in cloud storage
  4. Use catty download <label> to retrieve them anytime
Yes! Run multiple sessions in parallel for different projects. Use catty list to see all active sessions.

​
Files & Workspaces

100 MB. Use .gitignore to exclude large files, or use --no-upload and clone your repo in the session.
Workspaces save automatically:
  • First save: ~10 seconds after session start
  • Periodic saves: Every 30 seconds
  • Final save: When session stops
Download anytime with catty download <label>.
FeatureSync-backDownload
TimingReal-time during sessionOn-demand
Requires connectionYesNo
Use caseLive collaborationBackup/recovery
Sync-back happens automatically. Download is for retrieving files after the fact.

​
Secrets & GitHub

Set up a GitHub token:
catty secrets add github
This stores your token securely. Future sessions automatically have GitHub access.
Yes. Secrets are:
  • Encrypted with AES-256-GCM
  • Stored locally (never on Catty servers)
  • Machine-bound (can’t be decrypted elsewhere)
  • Only transmitted over HTTPS
With a token that has repo scope, Claude can:
  • Clone private repositories
  • Push commits
  • Create branches
  • Create pull requests
  • Manage issues

​
Security & Privacy

Yes. Each session runs in its own isolated cloud machine. Your workspace files exist only on that machine and in cloud storage (encrypted, accessible only to you).
Locally at ~/.catty/credentials.json with restricted permissions (0600). Credentials are only sent to the Catty API for authentication.
Your workspace is uploaded to the session machine and saved to cloud storage. However:
  • Only you can access your workspace data
  • Cloud storage is encrypted
  • Catty doesn’t analyze or process your code

​
Billing

Catty offers two plans:
  • Free tier: Limited usage per month
  • Pro: $25/month for higher limits
See Pricing for details.
No. Catty provides Claude API access. You don’t need your own API key.
No. Cloud compute costs are included in your plan. You only pay based on usage.

​
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 Troubleshooting for common issues
  • Open a GitHub issue for bugs
  • Review this FAQ for general questions