64017c6ca5
Run console:
- Picking a pipeline no longer pre-writes anything into the prompt box
(`promptPrefill` in `LaneConsolePane.tsx` is gone — it wrote the driving
slash command on a claude lane and a stage checklist on a codex one).
Whatever sits in that box is sent as a real prompt the moment the run
starts, so the box is the user's alone now.
- Resuming a session sends NO prompt at all (`handleStart` in `RunSetup.tsx`):
the resumed session carries its own transcript, and leftover text in the box
fired an extra turn into it.
Notifications:
- `client/src/lib/notify.ts` is now the ONE sender, used by both
`useNotifications` and Settings' test button, and it reports where the
notification landed: `POST /api/push/send` answering `{native:false,pushed:0}`
means it went NOWHERE, so the client falls back to a local notification
instead of counting the 200 as delivered.
- A notification carries the lane that raised it (`/workspace?lane=<id>`), and
Workspace selects that lane on arrival.
Profiles:
- `server/lib/cc-profiles.js` reads and writes the macOS login Keychain item
`Claude Code-credentials`, where the `claude` CLI actually keeps
`claudeAiOauth` on darwin — a switch used to rewrite a file nothing reads.
The file stays the fallback, is kept in step only when it already exists, and
`AGENTHUB_CC_KEYCHAIN=0` pins it (tests set it).
Tests: npm run test:server (1820 pass), client vitest (553 pass).
106 lines
3.5 KiB
JavaScript
106 lines
3.5 KiB
JavaScript
/**
|
|
* @description Service Worker for caching static assets and handling push notifications.
|
|
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
|
*/
|
|
|
|
// Bump this any time the SW logic changes - old clients will install the new
|
|
// SW, drop their existing caches in `activate`, and `skipWaiting` so the
|
|
// freshly-built bundle starts being served on the very next request.
|
|
const CACHE_NAME = "dashboard-v2";
|
|
|
|
self.addEventListener("install", () => {
|
|
// No pre-cache: network-first below means the cache fills lazily, and
|
|
// there's nothing to "warm" - the v1 SW was pre-caching `/`, which is
|
|
// exactly the file most likely to go stale after a rebuild.
|
|
self.skipWaiting();
|
|
});
|
|
|
|
self.addEventListener("activate", (event) => {
|
|
event.waitUntil(
|
|
caches
|
|
.keys()
|
|
.then((keys) =>
|
|
Promise.all(keys.filter((k) => k !== CACHE_NAME).map((k) => caches.delete(k)))
|
|
)
|
|
.then(() => self.clients.claim())
|
|
);
|
|
});
|
|
|
|
self.addEventListener("fetch", (event) => {
|
|
const { request } = event;
|
|
if (request.method !== "GET") return;
|
|
const url = new URL(request.url);
|
|
if (url.origin !== self.location.origin) return;
|
|
// Skip API, WebSocket, and Vite HMR endpoints
|
|
if (
|
|
url.pathname.startsWith("/api/") ||
|
|
url.pathname.startsWith("/ws") ||
|
|
url.pathname.includes("__vite")
|
|
)
|
|
return;
|
|
|
|
// Hashed bundles under /assets/ are immutable for a given URL - cache-first
|
|
// is safe and fast. A new build emits new filenames, so stale entries simply
|
|
// don't get re-requested.
|
|
if (url.pathname.startsWith("/assets/")) {
|
|
event.respondWith(
|
|
caches.match(request).then(
|
|
(cached) =>
|
|
cached ||
|
|
fetch(request).then((response) => {
|
|
if (response.ok && response.type === "basic") {
|
|
const clone = response.clone();
|
|
caches.open(CACHE_NAME).then((cache) => cache.put(request, clone));
|
|
}
|
|
return response;
|
|
})
|
|
)
|
|
);
|
|
return;
|
|
}
|
|
|
|
// Everything else (navigations, sw.js, manifest, icons, root /): network-first
|
|
// with cache fallback. The user always gets the freshest UI while online and
|
|
// a sensible fallback when offline.
|
|
event.respondWith(
|
|
fetch(request)
|
|
.then((response) => {
|
|
if (response.ok && response.type === "basic") {
|
|
const clone = response.clone();
|
|
caches.open(CACHE_NAME).then((cache) => cache.put(request, clone));
|
|
}
|
|
return response;
|
|
})
|
|
.catch(() => caches.match(request).then((c) => c || caches.match("/")))
|
|
);
|
|
});
|
|
|
|
// --- Push notifications (existing) ---
|
|
|
|
self.addEventListener("push", (event) => {
|
|
const data = event.data
|
|
? event.data.json()
|
|
: { title: "Agent Monitor", body: "New notification" };
|
|
const { title, ...options } = data;
|
|
event.waitUntil(self.registration.showNotification(title, { silent: false, ...options }));
|
|
});
|
|
|
|
self.addEventListener("notificationclick", (event) => {
|
|
event.notification.close();
|
|
const url = event.notification.data?.url;
|
|
event.waitUntil(
|
|
clients.matchAll({ type: "window" }).then((windowClients) => {
|
|
for (const client of windowClients) {
|
|
if ("focus" in client) {
|
|
// Reuse an already-open tab instead of stacking a new one — that's
|
|
// also why `navigate` (same-origin only) beats postMessage: it works
|
|
// even if the page hasn't wired up a listener for this.
|
|
if (url && "navigate" in client) client.navigate(url).catch(() => {});
|
|
return client.focus();
|
|
}
|
|
}
|
|
if (url && clients.openWindow) return clients.openWindow(url);
|
|
})
|
|
);
|
|
});
|