Frequently Asked Questions

How do I install Sweet! CLI?

Install from source (this repo):

python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
chmod +x sweet

Then verify it’s working:

./sweet --help

See our Getting Started guide for the full flow.

What are the system requirements?

Sweet! CLI requires:

• macOS 10.15+, Linux (glibc 2.31+), or Windows 10+ (WSL2)
• Python 3.8+ or Node.js 16+ (depending on installation method)
• At least 2GB RAM
• Internet connection for AI API calls

Do I need an AI API key?

By default, no — Sweet! CLI uses our billing relay (recommended). Just sign in:

sweet login

If you want to use your own API key, run with --no-billing and set:

export DEEPSEEK_API_KEY="your-key"

How does Sweet! CLI differ from other AI coding assistants?

Sweet! CLI is designed for autonomous engineering rather than just code completion. Key differences:

• Operates directly in your terminal - no IDE plugin required
• Can work independently on complex tasks for hours
• Makes technical decisions autonomously (architecture, libraries, approaches)
• Works with any codebase, language, or framework
• Follows software engineering best practices (TDD, git commits, error handling)

See our AI coding assistants comparison for a detailed analysis.

Can Sweet! CLI work offline?

Sweet! CLI requires an internet connection for AI model inference. However, some features work offline:

• Local file operations
• Git operations
• Shell command execution
• Codebase analysis (reading project files)

All AI-powered features require API calls to your chosen provider.

How do I resume an interrupted session?

Sweet! CLI automatically saves session state. To resume:

sweet resume

Or list recent sessions:

sweet sessions

To resume a specific session by ID:

sweet start --session <ID>

The CLI will restore todos, file context, and conversation history.

What programming languages are supported?

Sweet! CLI supports all programming languages. It doesn't require language-specific plugins - it uses AI models trained on hundreds of languages. Common languages include:

• JavaScript/TypeScript, Python, Java, C#, C++, Go, Rust
• HTML/CSS, SQL, Bash, PowerShell
• Framework-specific code (React, Django, Spring, etc.)
• Configuration files (YAML, JSON, TOML, XML)

How much does Sweet! CLI cost?

Sweet! CLI currently offers:

• Pro: $20/month
• Max: $200/month
• Trial: 3 days (credit card required via Stripe checkout)

See the latest details on our Billing page.

Which AI providers are included in the pricing?

Sweet! CLI uses the billing relay by default. The billing relay provides authenticated access to the backend models configured on the server, so you don’t need to manage provider keys locally.

If you want to bring your own key, run with --no-billing and use --provider deepseek|nebius.

How do I cancel or change my plan?

You can manage your subscription on the billing page. Sign in and use “Manage subscription”:

sweetcli.com/billing.html

Changes take effect at the end of your billing cycle.

Sweet! CLI is not responding to commands

Try these steps:

1. Verify you’re running from the repo root: ./sweet --help
2. If you’re using billing (recommended), sign in: ./sweet login
3. If you’re using --no-billing, ensure DEEPSEEK_API_KEY is set

If issues persist, see our Troubleshooting guide.

AI responses are slow or time out

Possible causes and solutions:

• Network issues: Check your internet connection
• Model choice: Try a smaller/faster model via --model (or use the billing relay defaults)
• Large tasks: Break the task into smaller steps

How do I report a bug or request a feature?

You can report issues in several ways:

• Submit an issue on our GitHub repository
• Email support: support@sweetcli.com

When reporting a bug, include the command you ran and any terminal output.

Is my code sent to AI providers?

Yes — Sweet! CLI sends relevant context to the model backend in order to generate responses. When using billing, requests go through the billing relay; in --no-billing mode, requests go directly to your configured provider.

• We never store your code on our servers
• API calls are encrypted end-to-end
• Check your provider’s privacy policy for data handling

For sensitive codebases, consider limiting what you share as context and using a provider with terms that fit your needs.

Can Sweet! CLI be used in enterprise environments?

Enterprise features (SSO/on‑prem/compliance) are not documented in this repo. Contact enterprise@sweetcli.com if you need enterprise support.

How are API keys stored?

Billing login tokens are stored locally in ~/.sweet/config.json.

If you use --no-billing, keep API keys in environment variables (recommended) rather than writing them to disk.