Opsera 解决的是一个很具体的问题：服务器在 VPN、堡垒机或内部网络后面时，AI 编码代理需要一个可控的本地通道来执行运维动作，而不是把原始 SSH 凭证直接贴进对话或脚本里。
它做什么
Opsera 提供本地服务器和凭证管理、加密凭证存储、命令运行、SFTP 上传下载、大文件分片上传、操作日志，以及面向 Codex、Claude Code、Gemini CLI 等本地代理的命令行入口。
最新重点
最近版本加入了可复用的 SSO agent。用户先通过官方 VPN/SSO 启动 Xshell，Opsera 再读取本机 Xshell/XshellCore 进程中的临时 SSH URL，建立并保持一条 SSH 连接。后续 command run --sso、file upload --sso、file download --sso 会优先复用这条连接。
边界
Opsera 不是完整堡垒机、权限系统或密钥管理平台。它不会替代组织内的安全流程，也不应该用来绕过访问控制。它的定位是把已经授权的本地连接整理成更适合 AI 代理调用的操作层。
& $opsera sso attach
& $opsera command run --sso "hostname && whoami"
& $opsera file upload --sso "D:\local\file.txt" "/root/file.txt"继续阅读
源码和发布包记录在 GitHub: https://github.com/tao-vin/opsera
共享跟帖
所有语言，共用一棵讨论树Update
SSO stability and transfer reliability update
Summary
Recent work focused on making Opsera's SSO agent more reliable, reducing false offline reports, and hardening large file transfer completion checks.
Progress
We improved the SSO agent so it now synchronizes with live Xshell sessions more reliably. Status checks can start and refresh the agent when a reusable Xshell URL is present, the agent clears failed-token cache when the Xshell URL changes, and health checks no longer confuse a slow status probe with an offline agent. Browser keepalive for the DASUSM page was also fixed and verified. Large uploads were tightened so completion requires chunk upload, remote merge, final size, SHA256 verification, and cleanup.
Problems
The main issue was inconsistent state: Xshell could be open while Opsera still showed offline, or the agent could be healthy while status reported it as not running. Browser keepalive was also being skipped because of a PowerShell variable conflict, and older large-upload behavior could return before the remote file was fully merged and verified.
Solutions
We added automatic SSO status synchronization with Xshell, separated lightweight readiness checks from full health checks, increased the health-check timeout, restored minimized browser windows before refreshing them, and made large uploads block until the final remote artifact is verified. The bundled Codex skill executable was rebuilt and replaced after each fix.
Next actions
Continue observing long-running sessions, keep the Xshell Enter keepalive as a fallback for environments that close idle terminals, and use upload-large for large release artifacts.
Update
Recent Opsera fixes, listed clearly
Summary
A clearer itemized summary of the recent Opsera stability and release work.
Progress
1. SSO status is now more accurate. `sso status` no longer reports the agent as offline just because a health check was slow.
2. The agent now syncs with Xshell automatically. If Xshell is open and a reusable SSH URL exists, status checks can start the agent and attach without needing a manual restart.
3. Stale SSH tokens are handled better. When the Xshell URL changes, Opsera clears its failed-token cache instead of staying stuck on old connection state.
4. DASUSM browser keepalive was fixed. The browser refresh job no longer fails on a PowerShell variable conflict, and minimized browser windows are restored before refresh.
5. Xshell keepalive remains available as a fallback. The helper sends a real Enter on a controlled interval to keep idle terminal sessions active when the environment requires it.
6. Large upload reliability was hardened. `upload-large --sso` now waits for chunk upload, remote merge, final size check, SHA256 verification, and cleanup before treating the upload as successful.
7. Codex skill deployment was updated. The rebuilt `opsera.exe` was copied into the local Codex skill so other agents use the fixed version.
8. Live verification passed. After stopping the agent, `sso status` was able to bring it back, report `opseraConnected:true`, and a live `--sso` command completed successfully.
Problems
The earlier summary was too dense. The technical fixes were correct, but the public update was harder to scan than it needed to be.
Solutions
This update restates the same work as a numbered progress list so readers can quickly see what changed and what was verified.
Next actions
Continue observing long-running SSO sessions and keep using the hardened `upload-large --sso` path for large release artifacts.