DeepSeek Harness Remote
DeepSeek Harness Remote 可將手機或另一台電腦與你運行 DeepSeek Harness 的電腦安全連接,隨時隨地繼續你的工作,方便隨時查看進度並繼續工作。
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Drafts attendance emails in Gmail. Login is checked by Vercel Functions in api/; each password maps to a sender (Gmail + name) kept in Vercel environment variables, which are never sent to the browser.
public/login.html — the only public pageapp/index.html — the app, served only by api/app.js to signed-in users (/ is rewritten there)api/login.js, api/logout.js, api/me.js — sign in, sign out, and the signed-in user's data/demo — guest mode: the same app with made-up people and addresses; no login, no real data, Gmail never opensSESSION_SECRET — 32+ random characters (e.g. from openssl rand -hex 32 or a password generator)USERS — JSON list of hashed passwords. Make it with tools/hash-passwords.html:
open that file in your browser, type each person's password (12+ chars, all different), click
Generate USERS value and paste the result. Hashing happens in your browser; the tool is not deployed.
[{"hash":"pbkdf2_sha256$100000$<salt>$<hash>","email":"[email protected]","name":"Person One"}]
MAIL_TO — e.g. Manager Name <[email protected]>MAIL_CC — always-Cc'd addresses, comma separated, e.g. Team Lead <[email protected]>MAIL_BCC — optional, always-Bcc'd addressesSESSION_HOURS — optional, default 12Changing or removing someone's hash in USERS (and redeploying) logs them out.
Changing SESSION_SECRET logs everyone out.
/login in Vercel → Firewall.USERS (names and emails only — hashes never leave the server).
To give someone a login without listing them on the page, add "listed": false to their entry.
Every signed-in user sees the full list.