Find your work in one place.
The optional app brings sessions from linked computers into one list. Open a terminal, invite a teammate, and keep control of who gets access.
On this page
1. Link your computer
Create or sign into your account at app.shell.online, then run this on the host computer. Complete the approval in your browser.
shell auth- Link this machine. Remote start is a separate choice during setup.
shell whoami- Check the linked account.
2. Open a session
Sessions started on linked machines appear in the app. Open one to view the same terminal. Tabs stay connected while you switch between them.
To decrypt a session, unlock your personal vault if it contains the password, or enter the session password. Seeing a listing alone does not reveal its encrypted contents.
shell password <ID>- Recover an active session password on its host computer. Treat the printed value as a secret.
3. Bring in a teammate
Invite the person to your organization, then assign or share the session as appropriate. Session responsibility, terminal passwords and MCP grants are different kinds of access.
For a plain browser share, give your teammate the complete link and password. If someone should only watch, create a read-only session.
Start sessions from the browser
Only an approved, online machine can accept a browser-start request. The process runs on that machine—not on an app server. Enabling this grants remote execution authority; choose it deliberately.
shell auth --allow-remote-start- Allow your signed-in browser to start sessions on this machine.
shell auth --no-remote-start- Link the account without allowing remote start, or withdraw that permission.
shell daemon status- Check the local listener.
shell daemon stop- Pause the listener. A later Shell command can start it again.
shell service uninstall- Remove the installed background service. This is separate from account access.
Use your personal vault
The vault is per account, not per organization. It stores encrypted password copies and unlocks in your browser with its password or a supported PRF passkey. Keep your recovery key somewhere safe.
A teammate does not automatically receive your vault. If every owner-held password and recovery copy is lost, the service cannot recover them.
Understand the session state
A session’s status describes reachability, not whether an agent completed its task.
- Online / Starting
- The host is connected or starting.
- Offline / Unavailable
- The app cannot currently reach a usable host. Check the machine before assuming the process stopped.
- Finished
- A known process exit. It is not proof that the requested work succeeded.
Automation is a separate permission
Owners can set team MCP, daily-briefing and briefing-sharing preferences in the app or CLI. The switches are independent.
In this release, daily-briefing consent can allow an updated host to publish an owner-encrypted title and existing response excerpt for a supported, explicitly resumed OpenCode conversation. It does not prompt an agent or generate a new summary. Team delivery and a team MCP gateway are not implemented. See the exact limits.
shell permissions <ID>- Read the session’s automation preferences.
shell permissions <ID> --daily-briefing=true- Change only daily-briefing consent.
shell briefings on --all- Set your default and enable it on your existing own sessions—not teammates’ sessions.
Account actions
Use the audit log to inspect recorded account activity. It is not a complete terminal transcript. Account settings also include data export and feedback.
For a machine without a browser, use shell auth --no-browser and follow the printed approval instructions. More account and service commands.