يعالج Opsera فجوة عملية واضحة: عندما يكون الخادم خلف VPN أو bastion host أو شبكة داخلية، يحتاج وكيل البرمجة المحلي إلى مسار مضبوط لتشغيل الأوامر من دون نسخ بيانات SSH الخام داخل المحادثة أو السكربتات.
ما الذي يفعله
يوفر Opsera إدارة محلية للخوادم وبيانات الاعتماد، وتخزينا مشفرا، وتشغيل أوامر، ورفع وتنزيل ملفات عبر SFTP، ورفع ملفات كبيرة على أجزاء، وسجلات عمليات، وواجهة CLI لوكلاء محليين مثل Codex وClaude Code وGemini CLI.
التركيز الأخير
أضاف الإصدار الأخير وكيلا قابلا لإعادة الاستخدام لـ SSO. يبدأ المستخدم Xshell أولا عبر مسار VPN أو SSO الرسمي. بعد ذلك يقرأ Opsera عنوان SSH المؤقت من عملية Xshell أو XshellCore المحلية، ويفتح اتصال SSH واحدا ويحافظ عليه. ثم تعيد أوامر command run --sso وfile upload --sso وfile download --sso استخدام هذا الاتصال أولا.
الحدود
Opsera ليس منصة bastion كاملة، ولا نظام صلاحيات، ولا مدير أسرار. لا ينبغي استخدامه لتجاوز قواعد الوصول. دوره هو تحويل اتصال محلي مصرح به مسبقا إلى طبقة عمليات يمكن للوكلاء استدعاؤها بضبط أوضح.
المصدر
الكود المصدري وملاحظات الإصدارات على 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.