Files
penguin-harness/packages/web
Yaowei Zheng 45bfae6e94 Initialize repository with harness code and assets
Initial import of all source code, config, and README assets: the
packages workspace (cli, core, server, web, docs, landing, skills),
build scripts, tooling config, and CI workflows.

Includes the data-layout revision made on this branch: the local data
root defaults to ~/.penguin/data (PENGUIN_HOME still overrides; the
installer keeps its binaries in ~/.penguin), and every Agent lives
under <project>/agents/<agent>/ — path helpers, the three
agent-enumeration scans, the system prompt, built-in Skills, tests
and docs all follow the new layout.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018ihk8iQuo3kv2aPjAYEPuR
2026-07-19 14:06:53 +08:00
..

@prismshadow/penguin-web

The PenguinHarness Web App — a React 19 + Vite + Tailwind CSS 4 SPA that renders the OmniMessage stream (same protocol and statistics as the CLI) and manages Agents, Skills, Models, usage and Traces. Feature tour: Web App Guide.

Layout

src/
├── main.tsx / app.tsx / router.tsx / styles.css
├── api/            # fetch wrapper, typed endpoint functions, EventSource (SSE) wrapper
├── state/          # auth / project / sessions / theme / locale contexts
├── lib/
│   ├── omni/       # OmniMessage stream → view-model reducer + connect-first/dedup controller
│   └── …           # formatting, i18n dictionaries (zh/en), attachments, helpers
├── components/     # ui primitives (modal, drawer, select, …) + app layout
└── features/       # chat / agents / skills / models / usage / traces / benchmark / admin

DTO types are imported type-only from @prismshadow/penguin-server/api; no server code enters the bundle. Rendering rules for streaming partials (start/delta/stop aggregation, complete-message replacement, origin-chain nesting into subagent cards) live in lib/omni/stream-model.ts, which is fully unit-tested.

Development

Prereqs: Node >= 24, pnpm; run pnpm install at the repo root first (core must be built — the root dev:* scripts handle that).

pnpm dev:server   # backend at 127.0.0.1:7364
pnpm dev:web      # Vite dev server at 127.0.0.1:7365; /api proxied (SSE passes through)

The proxy target defaults to http://127.0.0.1:7364 (PENGUIN_API_PROXY overrides). Auth is a same-origin HttpOnly cookie, so the proxy keeps everything same-origin.

pnpm --filter @prismshadow/penguin-web typecheck
pnpm --filter @prismshadow/penguin-web test        # vitest (pure logic)
pnpm --filter @prismshadow/penguin-web test:e2e    # Playwright against a mock LLM
pnpm --filter @prismshadow/penguin-web build       # vite build → dist/

Production

No separate static server needed: @prismshadow/penguin-server auto-hosts packages/web/dist (or PENGUIN_WEB_DIST) with an SPA fallback — build the web app, start the server, done. The published npm packages bundle the built front end.

Part of PenguinHarness · Apache-2.0