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.