Skip to main content
Most problems are small — the wrong port, a missing credential, an expired session, a VPN that dropped. This page collects the ones we see most often and what to check first. If none of these match, the Status indicator in the bottom status bar and the Logs tab in the bottom panel are where to look next. Between them you can usually see what the app is trying to do and where it’s failing. Start with the bottom status bar before you dig through settings. It shows whether Studio is connecting, online, actively running work, and which local network address it sees. If a problem is really a local-helper, network, or sync issue, the status bar usually gives you the first clue.

Sign-in

SymptomCheck
”Can’t sign in”Confirm internet connectivity. Confirm the email on your Altostrat account. Try signing in from the dashboard as a cross-check.
”Signed in but no organizations”Check with your organization admin; invitations are managed from the dashboard.
”Switching organizations does nothing”Refresh Studio. If it persists, sign out and sign back in.

Workspace

SymptomCheck
A file or host keeps replacing the tab you had openTurn off preview mode in Settings > Workspace, or pin the tab before opening other items.
Sidebar disappearedToggle the primary sidebar with Mod+B.
Copilot panel disappearedToggle Copilot with Mod+Shift+B.
Bottom panel disappearedToggle the bottom panel with Mod+J.
Search does not find something you expectTry the activity-specific filter first, then use the top search box. Some host files only appear after a host is selected or connected.

Terminal and sessions

SymptomCheck
Terminal tab opens but connection failsVerify host address and port. Verify the credential or key path. Confirm jump host if the device is behind one. Check VPN or firewall.
Authentication loopsRe-enter the credential; for SSH keys, confirm the private key is valid and isn’t encrypted with an unsupported passphrase.
Session hangs mid-commandConnection may be stalled. Try Enter to wake the session; if no response, close and reopen the tab.
Session recording is emptyThe session ended before output arrived. Re-run the command with a live session.
Host Connect button is disabledComplete the required host details and attach a Keychain credential. Studio does not store protocol credentials inline.
Host opens the wrong access methodSet the preferred protocol in the host editor. Double-click and quick-open use the preferred protocol.
A device is reachable only through a bastionSet the jump host on the SSH protocol instead of duplicating the target as a separate host.

SFTP

SymptomCheck
”SFTP unavailable”Confirm the SSH session is connected. Confirm the remote server has sftp-server enabled.
”Permission denied” on saveCheck the file’s mode and owner. Edit permissions via right-click → Properties if you have rights.

Diagnostics (ping, traceroute, packet capture)

SymptomCheck
Packet capture failsConfirm capture permissions on your interface (admin/sudo on most systems).
Ping and traceroute show nothingYour machine’s firewall may be blocking ICMP. Try from a host session instead.
Flow collector receives nothingConfirm exporters are sending to your machine and the port Studio is listening on.

Copilot

SymptomCheck
Copilot “cannot use tools”Open Status; confirm the local helper is green. If not, restart Studio.
Copilot misses obvious contextAttach the active tab or your selection explicitly.
Copilot’s response is cut offToken budget reached — ask Copilot to continue, or switch to a more capable model in Settings > AI.
Copilot keeps asking before tool callsCheck the response mode and permissions menu. Ask and Planning are intentionally conservative; Autopilot removes per-tool prompts and should be used only in controlled scopes.
Autopilot is enabled unexpectedlyOpen the response mode menu or Settings > AI and turn off Autopilot / YOLO mode.
Copilot is acting with too much confidenceSwitch to Planning, ask for read-only checks only, and attach the exact terminal selection or tab you want it to reason from.
Suggested chats are too frequentLower the chat suggestion behavior in Settings > AI by adjusting the chat suggestion threshold.

Files and artifacts

SymptomCheck
Can’t find an artifactOpen Files, enable generated artifact search, and filter by kind. Also search for the incident, host, or command that produced it.
Host files are emptySelect the host first and confirm the SSH session or host file access path is available.
An old report keeps showing upArchive it so it stays searchable but leaves the current working list.

Diagrams

SymptomCheck
”Diagram won’t save”Check for unsaved edits in a sub-panel; save or discard, then retry. Reloading the editor usually clears stuck state.
Shape picker missing a libraryNot every library surfaces in the toolbar by default. Use search inside the shape picker.

Calls

SymptomCheck
Poor audio or videoClose other bandwidth-heavy apps. Switch audio/video devices in the call controls.
No audio at allCheck your OS audio permissions for Studio.
Can’t share screenCheck OS screen-recording permissions for Studio.

Sync

SymptomCheck
”Studio is slow to sync”Check your network; large organizations take longer on first sign-in. Let it finish in the background.
Changes don’t appear on another deviceConfirm both devices are signed into the same organization.
Status stays on connectingCheck internet/VPN state, then restart Studio if the local helper does not recover.

Getting more help

If the tables above don’t cover what you’re seeing, the support channel inside your Altostrat dashboard is the fastest path forward. Include what you were doing, what you expected, and what you saw — a copy of the Logs tab output makes a big difference.

System requirements

Platforms, network reach, privileges, and limits.

Settings

Workspace, appearance, terminal, AI, and update preferences.