DeepSeek Harness Remote
DeepSeek Harness Remote 可將手機或另一台電腦與你運行 DeepSeek Harness 的電腦安全連接,隨時隨地繼續你的工作,方便隨時查看進度並繼續工作。
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Meeting Intelligence automated
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗AI meeting intelligence: upload or record a meeting, get a transcript (Deepgram), and a summary, action items, decisions, open questions, and sentiment (Gemini).
Next.js 14 (App Router) · Neon Postgres · Drizzle ORM · NextAuth.js (Auth.js v5, Google OAuth) · Deepgram + Gemini · Tailwind CSS v4 + shadcn/ui
Install dependencies (already done if you're reading this from the generated project):
npm install
Create a Neon database at neon.tech and copy its connection string.
Create a Google OAuth client at the Google Cloud Console:
http://localhost:3000/api/auth/callback/google (and your production URL equivalent)Copy .env.example to .env.local and fill in real values:
cp .env.example .env.local
DATABASE_URL — Neon connection stringNEXTAUTH_SECRET — generate with openssl rand -base64 32NEXTAUTH_URL — http://localhost:3000 locallyGOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET — from step 3DEEPGRAM_API_KEY — from console.deepgram.comGEMINI_API_KEY — from aistudio.google.com/apikeyPush the schema to Neon:
npm run db:migrate
(A migration is already generated at drizzle/0000_massive_johnny_storm.sql. db:migrate applies it. Use npm run db:generate after future schema changes, and npm run db:studio to browse data.)
Run the dev server:
npm run dev
Speaker voice recognition (enrolment + identification) runs through a
self-hosted Python microservice at voice-service/ using
SpeechBrain's ECAPA-TDNN speaker embedding model — no API keys or usage
limits. It must be running alongside the Next.js app in dev for voice
enrolment/identification to work; without it, those features fail closed
(the app still works, meetings just fall back to Gemini's speaker guesses).
Set up once:
cd voice-service
python -m venv .venv
.venv\Scripts\activate # or `source .venv/bin/activate` on macOS/Linux
pip install -r requirements.txt
Requires the ffmpeg binary on your PATH (used to normalize uploaded audio
before embedding).
Then, side by side with npm run dev, run:
npm run voice-service
which starts uvicorn main:app --port 8001 --reload. Set
VOICE_SERVICE_URL in .env.local (defaults to http://localhost:8001,
see .env.example) so the Next.js app knows where to reach it.
/api/meetings/upload and /api/meetings/analyze can take a while for long meetings — both routes are configured with maxDuration = 300. On Vercel, this requires a plan that supports extended function durations.