Web client

_skillet_webclient is the multi-user web front-end for skillet_agent. It pairs an Express server (a JSON + Server-Sent-Events API) with a set of Vite-built, framework-free TypeScript pages. Signed-in users chat with preset agents (replies streamed token-by-token), queue and schedule background jobs and crews, review deliverables in an inbox, and manage recurring schedules — all on top of the same engine the CLI drives.

It is a sibling package to _skillet_agent and depends on it directly (skillet_agent is a file:../_skillet_agent dependency), importing its AgentRunner, JobStore, JobWorkflow, ScheduleStore, and session-log classes.

Architecture

        browser
          │  HTTP + SSE
          ▼
┌─────────────────────────────┐
│  Express server (src/)      │
│   /auth/*   passport auth   │
│   /api/*    sessions, jobs, │
│             schedules, …    │
│   static    Vite-built dist/│
└──────────────┬──────────────┘
               │ imports skillet_agent, reads its SQLite DBs
               ▼
   _skillet_agent/outputs/*.sqlite   (users, sessions, job board)

• Server — Express 5 (src/server.ts). Sets up authentication, mounts the /api/* routers, and serves the built front-end from dist/. It is a pure UI/API layer over the job board — it does not run the dispatcher; you run that as a separate skillet_agent process.
• Client — public/ holds one folder per page (chat, inbox, job board, schedules, profile, login, pricing, landing). Each is plain DOM TypeScript bundled by Vite, styled with Bootstrap from a CDN. No React/Vue.
• Shared state — all persistence lives in _skillet_agent. The server opens the same SQLite files under _skillet_agent/outputs/: web users (.user_store.sqlite), express sessions (.web_sessions.sqlite), chat-session rehydration handles (.web_chat_handles.sqlite), conversation history (.agent_sessions.sqlite), and the shared job board (.skillet_jobs.sqlite).

What users can do

Next

• Running it — build, run, and the environment variables it needs.
• Authentication — local + Google sign-in, sessions, the admin model.
• Pages — what each page does.
• HTTP API — the full route table.