尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Chat with an assistant about a trip, get a personal itinerary app for it.
• Chat interviews, thinks, and writes a brief. No web search, so it stays quick.
• Builder never talks to anyone. It takes one brief, researches the
destination properly, and produces the itinerary through custom tools.
The renderer in renderer/render.js is shared with
tools/itinerary-generator in the vault repo, and turns one itinerary JSON
into the same app shape as the Phu Quoc trip it was extracted from.檢視完整 README ↗Chat with an assistant about a trip, get a personal itinerary app for it.
Two agents:
The renderer in renderer/render.js is shared with
tools/itinerary-generator in the vault repo, and turns one itinerary JSON
into the same app shape as the Phu Quoc trip it was extracted from.
The itinerary is never written to a database. It is replayed from the builder session's own event log, and the builder session id is recovered from the chat session's log. The event log is the database.
People are separated by an anonymous session id in their own localStorage.
No accounts, no links.
A build takes minutes, longer than a serverless function lives. /api/send
returns immediately and the client polls /api/state; each poll resolves
whatever tool calls are pending right now and returns. The chat keeps talking
while the builder is still researching.
Agents are persisted objects, created once:
node --env-file=.env setup/create-agent.js # first time only
node --env-file=.env setup/update-agent.js # to change a prompt
Ids live in lib/config.js. ANTHROPIC_API_KEY is read from the environment
if set, with a fallback in lib/config.js.
The agent's prompt and tool schemas live on Anthropic's servers, not in the
deploy. Editing lib/prompt.js, lib/editTools.js or any other tool schema
changes nothing anybody can see until update-agent.js runs. No build step
does it and a Vercel deploy will not. This has twice produced a change that
looks shipped, reads shipped in the diff, and is inert — so
GET /api/health?sources=1 reports chatAgent, which is either ok (vN) or
tells you exactly what has drifted and to run the script.
node --env-file=.env setup/test-builder.js # builder alone
node setup/test-ui.js # full flow through the real UI