Documentation
Documentation for remote server editing, support, and safer maintenance work
Use this documentation hub to move from first connection to confident day-to-day operations across explorer, editor, terminal, source control, Docker, databases, deployments, Jira, billing, Robbie AI, notifications, and migration workflows.
Documentation → AI
Robbie AI documentation, from credits to privacy.
This section covers how Robbie works, how workspace context is prepared, how local fallback behaves, how AI credits are applied, and how the AI Team fits into one assistant experience.
How Robbie works
Understand the one-conversation model, behind-the-scenes specialist prep, and where Robbie fits into the workspace.
Open guideAI credits
See what uses monthly AI credits, what stays on built-in help, and how credit-backed analysis is explained.
Open guideWorkspace context
Review how Robbie uses active files, selections, terminal output, and related workspace context safely.
Open guideLocal fallback
Learn when built-in help and local workspace explanations keep the experience moving even when provider analysis is limited.
Open guidePrivacy
Review how ServerDesk handles credentials, workspace data, and privacy-related contact routes.
Open guideAI Team
Meet Robbie plus the specialist AI Team and see how each role improves the final answer without creating extra chats.
Open guideQuick start
Go from first sign-in to a working explorer, editor, and terminal session in a few deliberate steps.
Read articleConnections
Enter the same connection details you trust in another SSH client, test them, and save the connection for Explorer and Terminal.
Read articleSSH keys
Use the correct private key, ensure the matching public key exists on the server, and validate key permissions when authentication fails.
Read articleExplorer
Start at the correct root path, expand folders deliberately, and keep the active server visible while you work.
Read articleEditor
Keep changes small, review context before saving, and treat live file edits as operational work rather than casual note-taking.
Read articleTerminal
Open the terminal beside your files, validate context first, then run the smallest command that answers the question in front of you.
Read articleSource Control
Source Control keeps changed files, staged work, Robbie reviews, and commit generation in one place so remote edits stay easier to reason about.
Read articleDocker
Use Docker Explorer to find failing containers fast, read logs, and move into terminal or Robbie analysis with context intact.
Read articleDatabases
Create a saved database connection, test it first, and use the Explorer to inspect schemas and queries without exposing raw backend errors.
Read articleDeployments
Deployments combines saved commands, run history, stdout and stderr logs, and failure analysis so releases stay visible instead of ad hoc.
Read articleJira
Jira in ServerDesk turns a ticket into a workspace plan instead of leaving the task context separate from the code and review flow.
Read articleRobbie AI
Robbie answers product questions without using AI credits and spends credits only when the request needs code, file, terminal, or error analysis.
Read articleNotifications
Notifications collect deployment events, AI activity, billing changes, and workspace warnings so you do not have to infer what happened from scattered UI state.
Read articleBilling
Billing questions usually come down to renewals, card updates, invoices, payment failures, and cancellation timing.
Read articleMigration
Export projects, preserve hidden config files, reconnect your real servers, and rebuild your daily workflow in the browser.
Read article