Requests keep their endpoint.
Method, URL, headers, body, response, history, and AI context stay attached to one controller-pinned API session.
03 Connections
Live sessions.Exact ownership.
Open the tool the work needs, then preserve its destination, lifecycle, and assistant context from first command to final close.
01 Connection workflow
From saved endpoint to exact session—in five deliberate moves.
- 01Save the destination
Organize devices, folders, authentication profiles, tags, and appearance without putting secret values in ordinary records.
- 02Open the right transport
Use embedded SSH for network devices or the platform-native PTY and shell for local terminal work.
- 03Shape the session
Reorder tabs, split exact SSH sessions, or detach a live SSH session into its own window.
- 04Keep other channels separate
Controller APIs, native portal webviews, and OS-launched RDP profiles keep their own purpose and state.
- 05Ask without retargeting
The assistant remains bound to the session captured at send time—even when you move elsewhere.
02 Beyond the terminal
Different channels. Different rules.
Native portal
Browser state stays browser state.
Remote management pages run in isolated child webviews. Portal cookies and storage are not copied into API authentication or terminal context.
Profiles, not a second RDP stack.
Palshell stores credential-free profile metadata and launches the operating system client, where OS policy remains authoritative.
