Termilino

Security

The credential boundary and sharing controls, explained precisely.

Credentials stay in Termilino

SSH authentication is handled locally by the application. Stored passwords and key passphrases use an AES-256-GCM vault on your Mac; selected private-key files are read locally. The Codex MCP interface does not return these secrets.

Set a master password for stronger protection of the local vault key. In automatic-unlock mode the device key is stored next to the data. Bookmarks and command text are not covered by the same secret-storage guarantee.

You choose what Codex can access

Share selected terminal tabs for viewing or control, pause new input, switch to private mode, or revoke access. Codex commands pass through the visible terminal. Access controls do not grant more remote-user privileges.

Terminal text may contain passwords, tokens or personal information printed by a server or command. Anything exposed in shared output can reach Codex and the selected AI service. Pause does not block reading; private mode does.

Server identity and updates

Verify a new server’s host-key fingerprint before trusting it. Review changed keys instead of accepting them automatically. Application updates use the existing updates.pwodev.com service and signed update packages; installation requires confirmation.