What we are building next

Email hello@termiyo.com with what you are trying to do, not just the feature you had in mind. The problem is more useful than the solution — twice now a request has turned out to be answered by something that already existed under a name nobody could find.

• Agent forwarding across a jump chain. Forwarding to the first hop works today. Carrying it through a chain needs the agent channel re-opened per hop, which is a protocol change rather than a setting.
• A second factor on the account. The vault is protected by a password only you have; the account that syncs it is not, and should be.
• Session recording playback. Sessions are already recorded and encrypted. What is missing is a player that replays them with their original timing.

• Post-quantum key exchange. Our SSH library does not implement sntrup761x25519-sha512, and writing our own post-quantum key exchange for a client people trust with production access is not a trade we are willing to make. We would rather say this than ship a switch that claims it.
• A signed Windows installer. The Windows build is a portable archive until code signing is in place. An unsigned installer that trips SmartScreen teaches people to click through exactly the warning that protects them.

• A web terminal. Running your keys in a browser tab means either sending them to a server or trusting every extension you have installed. Neither is a thing we want to be responsible for.
• Recovering a lost master password. There is no way to do this that does not mean we can read your vault. A password reset resets your account; your vault stays sealed, and we say so in the email itself.
• Storing credentials for the AI assistant. The assistant sees the command you asked about and, only if you turn it on, your recent commands. It never sees a key, a password, or the contents of a vault.