Archived
feat: add PWA install icon and uppercase branding
This commit is contained in:
Federico Jaramillo Martinez
+5
-5
@@ -4,7 +4,7 @@
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>Page not found — PI WEB</title>
|
||||
<meta name="description" content="The Pi Web page you requested does not exist." />
|
||||
<meta name="description" content="The PI WEB page you requested does not exist." />
|
||||
<meta name="robots" content="noindex" />
|
||||
<meta property="og:title" content="Page not found — PI WEB" />
|
||||
<meta property="og:image" content="/assets/pi-web-banner.png" />
|
||||
@@ -26,13 +26,13 @@
|
||||
<body class="error-page">
|
||||
<header class="site-header">
|
||||
<nav class="container nav" aria-label="Main navigation">
|
||||
<a class="brand" href="/" aria-label="Pi Web home">Pi Web</a>
|
||||
<a class="brand" href="/" aria-label="PI WEB home">PI WEB</a>
|
||||
<div class="nav-links">
|
||||
<a href="/remote-first.html">Remote-first</a>
|
||||
<a href="/install.html">Install</a>
|
||||
<a href="/plugins.html">Plugins</a>
|
||||
<a href="/faq.html">FAQ</a>
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="Pi Web on GitHub">
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="PI WEB on GitHub">
|
||||
<svg class="github-icon" viewBox="0 0 16 16" aria-hidden="true">
|
||||
<path
|
||||
fill="currentColor"
|
||||
@@ -65,7 +65,7 @@
|
||||
</h1>
|
||||
<p class="error-copy">The route was hallucinated, deleted, or never shipped.</p>
|
||||
<div class="error-actions">
|
||||
<a class="button primary" href="/">Back to Pi Web</a>
|
||||
<a class="button primary" href="/">Back to PI WEB</a>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
@@ -73,7 +73,7 @@
|
||||
|
||||
<footer class="site-footer">
|
||||
<div class="container footer-inner">
|
||||
<span>Pi Web · remote control for persistent Pi Coding Agent sessions.</span>
|
||||
<span>PI WEB · remote control for persistent Pi Coding Agent sessions.</span>
|
||||
<div class="footer-links">
|
||||
<a href="/install.html">Install</a>
|
||||
<a href="/plugins.html">Plugins</a>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024" role="img" aria-labelledby="title desc">
|
||||
<title id="title">piweb mark</title>
|
||||
<title id="title">PI WEB mark</title>
|
||||
<desc id="desc">A horizontal brand bar.</desc>
|
||||
<style>
|
||||
.bar { fill: #00f0d8; }
|
||||
|
||||
|
Before Width: | Height: | Size: 391 B After Width: | Height: | Size: 392 B |
+13
-13
@@ -4,7 +4,7 @@
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>PI WEB FAQ</title>
|
||||
<meta name="description" content="Answers for common Pi Web install and runtime issues." />
|
||||
<meta name="description" content="Answers for common PI WEB install and runtime issues." />
|
||||
<meta property="og:title" content="PI WEB FAQ" />
|
||||
<meta property="og:image" content="assets/pi-web-banner.png" />
|
||||
<link rel="icon" type="image/svg+xml" href="assets/favicon.svg" />
|
||||
@@ -25,13 +25,13 @@
|
||||
<body>
|
||||
<header class="site-header">
|
||||
<nav class="container nav" aria-label="Main navigation">
|
||||
<a class="brand" href="./" aria-label="Pi Web home">Pi Web</a>
|
||||
<a class="brand" href="./" aria-label="PI WEB home">PI WEB</a>
|
||||
<div class="nav-links">
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
<a href="install.html">Install</a>
|
||||
<a href="plugins.html">Plugins</a>
|
||||
<a href="faq.html" aria-current="page">FAQ</a>
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="Pi Web on GitHub">
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="PI WEB on GitHub">
|
||||
<svg class="github-icon" viewBox="0 0 16 16" aria-hidden="true">
|
||||
<path
|
||||
fill="currentColor"
|
||||
@@ -54,7 +54,7 @@
|
||||
<p class="eyebrow"><span class="pulse"></span> FAQ & troubleshooting</p>
|
||||
<h1>Fix the things that usually go wrong first.</h1>
|
||||
<p>
|
||||
Most Pi Web install issues are environment issues: systemd availability, PATH setup, Node version managers,
|
||||
Most PI WEB install issues are environment issues: systemd availability, PATH setup, Node version managers,
|
||||
or remote access expectations.
|
||||
</p>
|
||||
</div>
|
||||
@@ -81,7 +81,7 @@
|
||||
<article id="is-this-linux-only" class="faq-item">
|
||||
<h2>Is this Linux only?</h2>
|
||||
<p>
|
||||
No. Pi Web can run anywhere its runtime dependencies work, including macOS and Windows through WSL. The
|
||||
No. PI WEB can run anywhere its runtime dependencies work, including macOS and Windows through WSL. The
|
||||
automatic <code>pi-web install</code> command is the Linux-specific part because it writes and manages
|
||||
<code>systemctl --user</code> services.
|
||||
</p>
|
||||
@@ -96,8 +96,8 @@
|
||||
<article id="tools-are-not-found" class="faq-item">
|
||||
<h2>Tools are failing, node is not found, or Pi cannot find commands</h2>
|
||||
<p>
|
||||
The shell environment needs to be set up so login shells have the required PATH entries for Pi Web, Pi,
|
||||
and any tools your agents need. Pi Web services run commands through a non-interactive login shell, so
|
||||
The shell environment needs to be set up so login shells have the required PATH entries for PI WEB, Pi,
|
||||
and any tools your agents need. PI WEB services run commands through a non-interactive login shell, so
|
||||
an interactive terminal can work while services fail.
|
||||
</p>
|
||||
<div class="code-card">
|
||||
@@ -174,9 +174,9 @@
|
||||
</article>
|
||||
|
||||
<article id="public-internet" class="faq-item">
|
||||
<h2>Can I expose Pi Web to the public internet?</h2>
|
||||
<h2>Can I expose PI WEB to the public internet?</h2>
|
||||
<p>
|
||||
Do not expose it directly to the public internet. Pi Web assumes trusted users and trusted server paths.
|
||||
Do not expose it directly to the public internet. PI WEB assumes trusted users and trusted server paths.
|
||||
For remote access, bind only to an interface that is already private and controlled: for example the
|
||||
server's VPN IP, a private LAN IP, or localhost behind an SSH tunnel.
|
||||
</p>
|
||||
@@ -190,9 +190,9 @@
|
||||
</article>
|
||||
|
||||
<article id="laptop-or-server" class="faq-item">
|
||||
<h2>Should I run Pi Web on my laptop or a server?</h2>
|
||||
<h2>Should I run PI WEB on my laptop or a server?</h2>
|
||||
<p>
|
||||
You can run it locally, but Pi Web is most useful on a machine that stays on. A remote dev box, home
|
||||
You can run it locally, but PI WEB is most useful on a machine that stays on. A remote dev box, home
|
||||
server, cloud VM, or workstation gives agents a stable place to keep working while your laptop becomes
|
||||
just a client.
|
||||
</p>
|
||||
@@ -204,7 +204,7 @@
|
||||
</article>
|
||||
|
||||
<article id="plugins" class="faq-item">
|
||||
<h2>Can I use local plugins with production Pi Web?</h2>
|
||||
<h2>Can I use local plugins with production PI WEB?</h2>
|
||||
<p>
|
||||
Yes. Put trusted browser-side plugins in <code>~/.pi-web/plugins/<plugin-id>/</code>, or symlink a
|
||||
development folder there. Reload the browser tab after edits. If <code>PI_WEB_DATA_DIR</code> is set, use
|
||||
@@ -248,7 +248,7 @@
|
||||
|
||||
<footer class="site-footer">
|
||||
<div class="container footer-inner">
|
||||
<span>Pi Web FAQ</span>
|
||||
<span>PI WEB FAQ</span>
|
||||
<div class="footer-links">
|
||||
<a href="./">Home</a>
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
|
||||
+11
-11
@@ -6,7 +6,7 @@
|
||||
<title>PI WEB — persistent AI coding agents in your browser</title>
|
||||
<meta
|
||||
name="description"
|
||||
content="Pi Web is a browser control plane for persistent Pi Coding Agent sessions running on your own machine or server."
|
||||
content="PI WEB is a browser control plane for persistent Pi Coding Agent sessions running on your own machine or server."
|
||||
/>
|
||||
<meta property="og:title" content="PI WEB" />
|
||||
<meta
|
||||
@@ -32,13 +32,13 @@
|
||||
<body class="home-page">
|
||||
<header class="site-header">
|
||||
<nav class="container nav" aria-label="Main navigation">
|
||||
<a class="brand" href="./" aria-label="Pi Web home">Pi Web</a>
|
||||
<a class="brand" href="./" aria-label="PI WEB home">PI WEB</a>
|
||||
<div class="nav-links">
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
<a href="install.html">Install</a>
|
||||
<a href="plugins.html">Plugins</a>
|
||||
<a href="faq.html">FAQ</a>
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="Pi Web on GitHub">
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="PI WEB on GitHub">
|
||||
<svg class="github-icon" viewBox="0 0 16 16" aria-hidden="true">
|
||||
<path
|
||||
fill="currentColor"
|
||||
@@ -71,7 +71,7 @@
|
||||
</span>
|
||||
</h1>
|
||||
<p class="hero-lede">
|
||||
Pi Web runs Pi Coding Agent sessions in real server-side workspaces, keeps them alive when your browser
|
||||
PI WEB runs Pi Coding Agent sessions in real server-side workspaces, keeps them alive when your browser
|
||||
leaves, and gives you a fast web surface to supervise, redirect, and review the work.
|
||||
</p>
|
||||
<p class="hero-manifesto">
|
||||
@@ -89,7 +89,7 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="terminal" aria-label="Pi Web install preview">
|
||||
<aside class="terminal" aria-label="PI WEB install preview">
|
||||
<div class="terminal-top">
|
||||
<div class="dots"><span></span><span></span><span></span></div>
|
||||
<span>agent-hub.local</span>
|
||||
@@ -116,7 +116,7 @@
|
||||
<strong>Workspaces, sessions, transcripts, terminals — one agent control plane.</strong>
|
||||
<span>Bring your own repositories.</span>
|
||||
</div>
|
||||
<img src="assets/pi-web-demo.gif" alt="Pi Web browser UI demo" />
|
||||
<img src="assets/pi-web-demo.gif" alt="PI WEB browser UI demo" />
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
@@ -128,7 +128,7 @@
|
||||
<h2>Your laptop is a window, not the workstation.</h2>
|
||||
<p>
|
||||
Local-only development can become the blocker: one device owns the tools, terminals, build cache, editor,
|
||||
and agent runtime. Pi Web moves the working environment to a machine that stays on, so agents can keep
|
||||
and agent runtime. PI WEB moves the working environment to a machine that stays on, so agents can keep
|
||||
making progress while every browser becomes a control surface.
|
||||
</p>
|
||||
</div>
|
||||
@@ -245,8 +245,8 @@
|
||||
<article class="doc-card">
|
||||
<h3>macOS and WSL?</h3>
|
||||
<p>
|
||||
Pi Web itself is not Linux-only. The one-command service installer targets Linux systemd. macOS and WSL can
|
||||
run Pi Web manually; WSL with systemd can use the installer too.
|
||||
PI WEB itself is not Linux-only. The one-command service installer targets Linux systemd. macOS and WSL can
|
||||
run PI WEB manually; WSL with systemd can use the installer too.
|
||||
</p>
|
||||
<a href="faq.html#is-this-linux-only">Read compatibility notes →</a>
|
||||
</article>
|
||||
@@ -261,7 +261,7 @@
|
||||
<article class="doc-card">
|
||||
<h3>Node or tools not found?</h3>
|
||||
<p>
|
||||
Services run login shells. If tools work in your interactive terminal but not in Pi Web, fix PATH in your
|
||||
Services run login shells. If tools work in your interactive terminal but not in PI WEB, fix PATH in your
|
||||
login shell startup files and run the doctor command.
|
||||
</p>
|
||||
<a href="faq.html#tools-are-not-found">Fix PATH issues →</a>
|
||||
@@ -272,7 +272,7 @@
|
||||
|
||||
<footer class="site-footer">
|
||||
<div class="container footer-inner">
|
||||
<span>Pi Web · remote control for persistent Pi Coding Agent sessions.</span>
|
||||
<span>PI WEB · remote control for persistent Pi Coding Agent sessions.</span>
|
||||
<div class="footer-links">
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
<a href="install.html">Install</a>
|
||||
|
||||
+15
-15
@@ -4,7 +4,7 @@
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>Install PI WEB</title>
|
||||
<meta name="description" content="Complete installation guide for Pi Web on Linux, macOS, and Windows WSL." />
|
||||
<meta name="description" content="Complete installation guide for PI WEB on Linux, macOS, and Windows WSL." />
|
||||
<meta property="og:title" content="Install PI WEB" />
|
||||
<meta property="og:image" content="assets/pi-web-banner.png" />
|
||||
<link rel="icon" type="image/svg+xml" href="assets/favicon.svg" />
|
||||
@@ -25,13 +25,13 @@
|
||||
<body>
|
||||
<header class="site-header">
|
||||
<nav class="container nav" aria-label="Main navigation">
|
||||
<a class="brand" href="./" aria-label="Pi Web home">Pi Web</a>
|
||||
<a class="brand" href="./" aria-label="PI WEB home">PI WEB</a>
|
||||
<div class="nav-links">
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
<a href="install.html" aria-current="page">Install</a>
|
||||
<a href="plugins.html">Plugins</a>
|
||||
<a href="faq.html">FAQ</a>
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="Pi Web on GitHub">
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="PI WEB on GitHub">
|
||||
<svg class="github-icon" viewBox="0 0 16 16" aria-hidden="true">
|
||||
<path
|
||||
fill="currentColor"
|
||||
@@ -52,10 +52,10 @@
|
||||
<section class="page-hero">
|
||||
<div class="container">
|
||||
<p class="eyebrow"><span class="pulse"></span> Installation guide</p>
|
||||
<h1>Get Pi Web running where your agents work.</h1>
|
||||
<h1>Get PI WEB running where your agents work.</h1>
|
||||
<p>
|
||||
The best production-style setup is a Linux machine with user-level systemd services. macOS and Windows WSL
|
||||
are useful too: run the two Pi Web processes manually, or use the installer in WSL when systemd is enabled.
|
||||
are useful too: run the two PI WEB processes manually, or use the installer in WSL when systemd is enabled.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
@@ -86,7 +86,7 @@
|
||||
</ul>
|
||||
<div class="callout warning">
|
||||
<strong>Important PATH detail:</strong>
|
||||
Pi Web services run through your login shell with <code>-lc</code>. Setup that only lives in interactive shell
|
||||
PI WEB services run through your login shell with <code>-lc</code>. Setup that only lives in interactive shell
|
||||
files or prompt hooks may not be visible to services. Run <code>pi-web doctor</code> after installing.
|
||||
</div>
|
||||
</section>
|
||||
@@ -125,8 +125,8 @@
|
||||
|
||||
<section id="pi-package">
|
||||
<h2>Install through Pi</h2>
|
||||
<p>Pi Web is also published as a Pi package. This exposes a <code>/pi-web</code> command inside Pi.</p>
|
||||
<p>When installed this way, <code>/pi-web install</code> can use Pi Web's package-local service entrypoints, so <code>pi-web-server</code> and <code>pi-web-sessiond</code> do not need to be on your shell <code>PATH</code>.</p>
|
||||
<p>PI WEB is also published as a Pi package. This exposes a <code>/pi-web</code> command inside Pi.</p>
|
||||
<p>When installed this way, <code>/pi-web install</code> can use PI WEB's package-local service entrypoints, so <code>pi-web-server</code> and <code>pi-web-sessiond</code> do not need to be on your shell <code>PATH</code>.</p>
|
||||
<div class="code-card">
|
||||
<div class="copy-row">
|
||||
<strong>Pi package path</strong>
|
||||
@@ -145,7 +145,7 @@
|
||||
<section id="manual-run">
|
||||
<h2>macOS / WSL manual run</h2>
|
||||
<p>
|
||||
Pi Web is not Linux-only, but the <code>pi-web install</code> service setup is Linux/systemd-specific. On macOS
|
||||
PI WEB is not Linux-only, but the <code>pi-web install</code> service setup is Linux/systemd-specific. On macOS
|
||||
or WSL without systemd, install the package and run the daemon and web server yourself.
|
||||
</p>
|
||||
<div class="code-card">
|
||||
@@ -170,7 +170,7 @@
|
||||
<section id="remote-access">
|
||||
<h2>Remote access</h2>
|
||||
<p>
|
||||
Pi Web binds to <code>127.0.0.1:8504</code> by default. For a remote server, the safest option is an SSH
|
||||
PI WEB binds to <code>127.0.0.1:8504</code> by default. For a remote server, the safest option is an SSH
|
||||
tunnel:
|
||||
</p>
|
||||
<div class="code-card">
|
||||
@@ -182,8 +182,8 @@
|
||||
<span class="comment"># Open http://127.0.0.1:8504 on your local machine</span></code></pre>
|
||||
</div>
|
||||
<div class="callout danger">
|
||||
Pi Web is designed for trusted users and trusted server paths. Do not expose it directly to the public
|
||||
internet. If you use a VPN or private network, bind Pi Web to the server's VPN/private IP, such as a
|
||||
PI WEB is designed for trusted users and trusted server paths. Do not expose it directly to the public
|
||||
internet. If you use a VPN or private network, bind PI WEB to the server's VPN/private IP, such as a
|
||||
Tailscale/WireGuard/LAN address, and make sure that network policy limits access. Avoid
|
||||
<code>0.0.0.0</code> unless a firewall, VPN, or authenticated reverse proxy strictly controls the port.
|
||||
</div>
|
||||
@@ -225,7 +225,7 @@
|
||||
}</code></pre>
|
||||
</div>
|
||||
<p>
|
||||
The web server defaults to <code>127.0.0.1:8504</code> and stores Pi Web state in <code>~/.pi-web</code>.
|
||||
The web server defaults to <code>127.0.0.1:8504</code> and stores PI WEB state in <code>~/.pi-web</code>.
|
||||
</p>
|
||||
<ul>
|
||||
<li><code>PI_WEB_CONFIG</code>: path to a config JSON file. Defaults to <code>~/.config/pi-web/config.json</code>.</li>
|
||||
@@ -250,7 +250,7 @@
|
||||
<pre id="uninstall-commands"><code><span class="prompt">$</span> pi-web uninstall
|
||||
<span class="prompt">$</span> npm uninstall -g @jmfederico/pi-web</code></pre>
|
||||
</div>
|
||||
<p>Optional cleanup, if you also want to delete Pi Web config and state:</p>
|
||||
<p>Optional cleanup, if you also want to delete PI WEB config and state:</p>
|
||||
<div class="code-card">
|
||||
<div class="copy-row">
|
||||
<strong>Delete config and data</strong>
|
||||
@@ -277,7 +277,7 @@
|
||||
|
||||
<footer class="site-footer">
|
||||
<div class="container footer-inner">
|
||||
<span>Pi Web docs</span>
|
||||
<span>PI WEB docs</span>
|
||||
<div class="footer-links">
|
||||
<a href="./">Home</a>
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
|
||||
+19
-19
@@ -4,7 +4,7 @@
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>PI WEB plugins</title>
|
||||
<meta name="description" content="Use and develop trusted local Pi Web UI plugins." />
|
||||
<meta name="description" content="Use and develop trusted local PI WEB UI plugins." />
|
||||
<meta property="og:title" content="PI WEB plugins" />
|
||||
<meta property="og:image" content="assets/pi-web-banner.png" />
|
||||
<link rel="icon" type="image/svg+xml" href="assets/favicon.svg" />
|
||||
@@ -25,13 +25,13 @@
|
||||
<body>
|
||||
<header class="site-header">
|
||||
<nav class="container nav" aria-label="Main navigation">
|
||||
<a class="brand" href="./" aria-label="Pi Web home">Pi Web</a>
|
||||
<a class="brand" href="./" aria-label="PI WEB home">PI WEB</a>
|
||||
<div class="nav-links">
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
<a href="install.html">Install</a>
|
||||
<a href="plugins.html" aria-current="page">Plugins</a>
|
||||
<a href="faq.html">FAQ</a>
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="Pi Web on GitHub">
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="PI WEB on GitHub">
|
||||
<svg class="github-icon" viewBox="0 0 16 16" aria-hidden="true">
|
||||
<path
|
||||
fill="currentColor"
|
||||
@@ -52,10 +52,10 @@
|
||||
<section class="page-hero">
|
||||
<div class="container">
|
||||
<p class="eyebrow"><span class="pulse"></span> Plugin development</p>
|
||||
<h1>Customize Pi Web with local UI plugins.</h1>
|
||||
<h1>Customize PI WEB with local UI plugins.</h1>
|
||||
<p>
|
||||
Plugins are trusted browser-side ES modules. They can add actions, workspace panels, and compact workspace
|
||||
labels to the Pi Web UI.
|
||||
labels to the PI WEB UI.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
@@ -76,13 +76,13 @@
|
||||
<div class="doc-content">
|
||||
<section id="extend">
|
||||
<h2>What can be extended</h2>
|
||||
<p>Plugins can add small, focused UI extensions to Pi Web:</p>
|
||||
<p>Plugins can add small, focused UI extensions to PI WEB:</p>
|
||||
<ul>
|
||||
<li><strong>Action palette commands</strong> for custom workflows.</li>
|
||||
<li><strong>Workspace tools and panels</strong> next to Files, Git, and Terminal.</li>
|
||||
<li><strong>Workspace labels</strong> in the workspace list, header, and status bar.</li>
|
||||
<li><strong>Static assets</strong> served from the plugin folder.</li>
|
||||
<li><strong>Browser-side integrations</strong> using Pi Web HTTP/WebSocket APIs.</li>
|
||||
<li><strong>Browser-side integrations</strong> using PI WEB HTTP/WebSocket APIs.</li>
|
||||
</ul>
|
||||
<p>
|
||||
Plugins cannot extend the session daemon or add server-side hooks. They run in the browser UI only.
|
||||
@@ -98,7 +98,7 @@
|
||||
<h2>What to ask AI to build</h2>
|
||||
<p>
|
||||
You do not need to hand-code plugins. Give an AI agent a clear goal, the workspace/project facts it
|
||||
should use, and the Pi Web plugin rules.
|
||||
should use, and the PI WEB plugin rules.
|
||||
</p>
|
||||
<ul>
|
||||
<li>Show a workspace badge from a repo file, environment file, branch name, container, or dev URL.</li>
|
||||
@@ -111,24 +111,24 @@
|
||||
<strong>Prompt: create a plugin</strong>
|
||||
<button class="copy-button" data-copy="#plugin-create-prompt">Copy</button>
|
||||
</div>
|
||||
<pre id="plugin-create-prompt"><code>Build a Pi Web plugin for this project.
|
||||
<pre id="plugin-create-prompt"><code>Build a PI WEB plugin for this project.
|
||||
Goal: <describe the UI behavior>.
|
||||
Before coding, read the Pi Web plugin docs:
|
||||
Before coding, read the PI WEB plugin docs:
|
||||
https://pi-web.dev/plugins.html
|
||||
Full API reference:
|
||||
https://pi-web.dev/plugins.md
|
||||
Create it as a local plugin under ~/.pi-web/plugins/<plugin-id>.
|
||||
Use the appropriate extension points from the docs.
|
||||
Validate by checking /pi-web-plugins/manifest.json and explain how to reload/debug it.
|
||||
Do not modify Pi Web itself.</code></pre>
|
||||
Do not modify PI WEB itself.</code></pre>
|
||||
</div>
|
||||
<div class="code-card">
|
||||
<div class="copy-row">
|
||||
<strong>Prompt: improve a plugin</strong>
|
||||
<button class="copy-button" data-copy="#plugin-improve-prompt">Copy</button>
|
||||
</div>
|
||||
<pre id="plugin-improve-prompt"><code>Improve the Pi Web plugin at <path>.
|
||||
Before coding, read the Pi Web plugin docs:
|
||||
<pre id="plugin-improve-prompt"><code>Improve the PI WEB plugin at <path>.
|
||||
Before coding, read the PI WEB plugin docs:
|
||||
https://pi-web.dev/plugins.html
|
||||
Full API reference:
|
||||
https://pi-web.dev/plugins.md
|
||||
@@ -140,11 +140,11 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
<section id="example">
|
||||
<h2>Canonical example</h2>
|
||||
<p>
|
||||
Pi Web ships a real bundled <strong>Info</strong> plugin. It is intentionally small while still using all
|
||||
PI WEB ships a real bundled <strong>Info</strong> plugin. It is intentionally small while still using all
|
||||
core contribution types: one action, one workspace label, and one workspace panel.
|
||||
</p>
|
||||
<p>
|
||||
Bundled Pi Web plugins are developed as TypeScript in the repository, while their package metadata
|
||||
Bundled PI WEB plugins are developed as TypeScript in the repository, while their package metadata
|
||||
points at the built JavaScript ES modules that the browser loads. <code>npm run dev:web</code> watches and
|
||||
rebuilds bundled plugin TS into <code>dist/pi-web-plugins/</code> during development, and <code>npm run build</code>
|
||||
emits JS before release packaging.
|
||||
@@ -169,7 +169,7 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
<h2>Production usage</h2>
|
||||
<p>
|
||||
Local plugins work with the production npm/systemd install. Put each plugin under
|
||||
<code>~/.pi-web/plugins/<plugin-id>/</code>, or symlink it there while developing. No Pi Web rebuild or
|
||||
<code>~/.pi-web/plugins/<plugin-id>/</code>, or symlink it there while developing. No PI WEB rebuild or
|
||||
session-daemon restart is required.
|
||||
</p>
|
||||
<div class="callout warning">
|
||||
@@ -195,7 +195,7 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
<p>
|
||||
If you want to understand the API yourself, ask an agent to read that file and explain the relevant
|
||||
extension points for the plugin you want. The Markdown reference also marks which context fields are
|
||||
stable and which Pi Web internals should be avoided unless necessary.
|
||||
stable and which PI WEB internals should be avoided unless necessary.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
@@ -223,7 +223,7 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
<section id="trust">
|
||||
<h2>Trust model</h2>
|
||||
<p>
|
||||
Plugins are not sandboxed. They run as JavaScript in the browser, can call Pi Web APIs available to the
|
||||
Plugins are not sandboxed. They run as JavaScript in the browser, can call PI WEB APIs available to the
|
||||
current session, and can render arbitrary UI. Install only plugins you trust.
|
||||
</p>
|
||||
<p>
|
||||
@@ -237,7 +237,7 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
|
||||
<footer class="site-footer">
|
||||
<div class="container footer-inner">
|
||||
<span>Pi Web plugin docs</span>
|
||||
<span>PI WEB plugin docs</span>
|
||||
<div class="footer-links">
|
||||
<a href="./">Home</a>
|
||||
<a href="remote-first.html">Remote-first</a>
|
||||
|
||||
+41
-41
@@ -1,13 +1,13 @@
|
||||
# Pi Web plugin API
|
||||
# PI WEB plugin API
|
||||
|
||||
Pi Web plugins are trusted browser-side ES modules that extend the Pi Web UI. They are intended for personal, team, and project-local customization, and simple enough for an LLM to create or modify directly.
|
||||
PI WEB plugins are trusted browser-side ES modules that extend the PI WEB UI. They are intended for personal, team, and project-local customization, and simple enough for an LLM to create or modify directly.
|
||||
|
||||
Plugins can currently:
|
||||
|
||||
- add action-palette commands;
|
||||
- add workspace tools/panels next to Files, Git, and Terminal;
|
||||
- add compact workspace-label items in the workspace list, panel header, and status bar;
|
||||
- call browser APIs and Pi Web HTTP/WebSocket APIs available to the current browser session;
|
||||
- call browser APIs and PI WEB HTTP/WebSocket APIs available to the current browser session;
|
||||
- serve their own static assets from the plugin directory.
|
||||
|
||||
They do **not** run in the session daemon, do not get a server-side hook API, and are not sandboxed.
|
||||
@@ -17,8 +17,8 @@ They do **not** run in the session daemon, do not get a server-side hook API, an
|
||||
Plugins run as JavaScript in the browser app. Treat them as trusted code:
|
||||
|
||||
- they can call browser APIs;
|
||||
- they can `fetch()` Pi Web API endpoints using the current browser access;
|
||||
- they can read workspace files through Pi Web's file endpoints if the UI can read them;
|
||||
- they can `fetch()` PI WEB API endpoints using the current browser access;
|
||||
- they can read workspace files through PI WEB's file endpoints if the UI can read them;
|
||||
- they can render arbitrary Lit templates/custom elements in plugin contribution areas;
|
||||
- they should not be installed from untrusted sources.
|
||||
|
||||
@@ -37,23 +37,23 @@ Good plugin requests:
|
||||
Copy-paste prompt for creating a plugin:
|
||||
|
||||
```text
|
||||
Build a Pi Web plugin for this project.
|
||||
Build a PI WEB plugin for this project.
|
||||
Goal: <describe the UI behavior>.
|
||||
Before coding, read the Pi Web plugin docs:
|
||||
Before coding, read the PI WEB plugin docs:
|
||||
https://pi-web.dev/plugins.html
|
||||
Full API reference:
|
||||
https://pi-web.dev/plugins.md
|
||||
Create it as a local plugin under ~/.pi-web/plugins/<plugin-id>.
|
||||
Use the appropriate extension points from the docs.
|
||||
Validate by checking /pi-web-plugins/manifest.json and explain how to reload/debug it.
|
||||
Do not modify Pi Web itself.
|
||||
Do not modify PI WEB itself.
|
||||
```
|
||||
|
||||
Copy-paste prompt for modifying a plugin:
|
||||
|
||||
```text
|
||||
Improve the Pi Web plugin at <path>.
|
||||
Before coding, read the Pi Web plugin docs:
|
||||
Improve the PI WEB plugin at <path>.
|
||||
Before coding, read the PI WEB plugin docs:
|
||||
https://pi-web.dev/plugins.html
|
||||
Full API reference:
|
||||
https://pi-web.dev/plugins.md
|
||||
@@ -63,9 +63,9 @@ After editing, check the manifest endpoint and browser-console failure cases.
|
||||
|
||||
## Canonical example: bundled Info plugin
|
||||
|
||||
Pi Web ships a real bundled `info` plugin. Use it as the reference example because it is intentionally small while still exercising all core contribution types: an action, a workspace label, and a workspace panel.
|
||||
PI WEB ships a real bundled `info` plugin. Use it as the reference example because it is intentionally small while still exercising all core contribution types: an action, a workspace label, and a workspace panel.
|
||||
|
||||
Bundled Pi Web plugins are developed as TypeScript in the repository, but their `package.json` metadata still points at built JavaScript because plugins are loaded by the browser as JS ES modules. `npm run dev:web` watches and rebuilds bundled plugin TS into `dist/pi-web-plugins/` during development, and `npm run build` emits the JS before packaging a release.
|
||||
Bundled PI WEB plugins are developed as TypeScript in the repository, but their `package.json` metadata still points at built JavaScript because plugins are loaded by the browser as JS ES modules. `npm run dev:web` watches and rebuilds bundled plugin TS into `dist/pi-web-plugins/` during development, and `npm run build` emits the JS before packaging a release.
|
||||
|
||||
Source files:
|
||||
|
||||
@@ -112,20 +112,20 @@ export default {
|
||||
|
||||
When copying the Info plugin, choose a new plugin id so it does not conflict with the bundled `info` plugin.
|
||||
|
||||
Pi Web also ships a `pi-web` status plugin that demonstrates dynamic `visible` and `badge` callbacks for tabs that only appear when the host has status messages or needs extra install visibility.
|
||||
PI WEB also ships a `pi-web` status plugin that demonstrates dynamic `visible` and `badge` callbacks for tabs that only appear when the host has status messages or needs extra install visibility.
|
||||
|
||||
## Local plugin usage
|
||||
|
||||
This works with the production npm/systemd install. Pi Web discovers plugins from `~/.pi-web/plugins/<plugin-package>/` on the web/API side; no Pi Web rebuild or session-daemon restart is required. If `PI_WEB_DATA_DIR` is set, use `$PI_WEB_DATA_DIR/plugins` instead.
|
||||
This works with the production npm/systemd install. PI WEB discovers plugins from `~/.pi-web/plugins/<plugin-package>/` on the web/API side; no PI WEB rebuild or session-daemon restart is required. If `PI_WEB_DATA_DIR` is set, use `$PI_WEB_DATA_DIR/plugins` instead.
|
||||
|
||||
Symlink a plugin folder into Pi Web's local plugin directory:
|
||||
Symlink a plugin folder into PI WEB's local plugin directory:
|
||||
|
||||
```bash
|
||||
mkdir -p ~/.pi-web/plugins
|
||||
ln -s /path/to/plugin-folder ~/.pi-web/plugins/plugin-id
|
||||
```
|
||||
|
||||
Reload the Pi Web browser tab. Pi Web serves plugin modules with an mtime-based `?v=` cache buster. After editing a plugin, hard reload the browser if you do not see changes.
|
||||
Reload the PI WEB browser tab. PI WEB serves plugin modules with an mtime-based `?v=` cache buster. After editing a plugin, hard reload the browser if you do not see changes.
|
||||
|
||||
## First-party separate plugin packages
|
||||
|
||||
@@ -133,11 +133,11 @@ First-party plugins that are published as their own npm packages can live in thi
|
||||
|
||||
A separate plugin package should:
|
||||
|
||||
- use type-only imports from `@jmfederico/pi-web/plugin-api` when it needs shared Pi Web plugin interfaces; this subpath is currently a `.d.ts`-only dogfooding surface, not a runtime JavaScript module;
|
||||
- keep its Pi Web metadata in its own `package.json` with `piWeb.plugins` entries pointing at built JavaScript in `dist/`;
|
||||
- use type-only imports from `@jmfederico/pi-web/plugin-api` when it needs shared PI WEB plugin interfaces; this subpath is currently a `.d.ts`-only dogfooding surface, not a runtime JavaScript module;
|
||||
- keep its PI WEB metadata in its own `package.json` with `piWeb.plugins` entries pointing at built JavaScript in `dist/`;
|
||||
- include a package-level `build` script and `prepack` script so `npm pack --workspace <package>` and `npm publish --workspace <package>` produce a usable plugin package;
|
||||
- use a local symlink into `~/.pi-web/plugins/<plugin-id>` while developing;
|
||||
- document any private Pi Web APIs it dogfoods until those APIs become stable plugin runtime helpers.
|
||||
- document any private PI WEB APIs it dogfoods until those APIs become stable plugin runtime helpers.
|
||||
|
||||
Typical local development loop from this repository:
|
||||
|
||||
@@ -146,13 +146,13 @@ npm run dev
|
||||
curl http://127.0.0.1:8504/pi-web-plugins/manifest.json
|
||||
```
|
||||
|
||||
The main Pi Web `dev` command watches bundled plugins in `pi-web-plugins/`, builds/watches separate plugin packages in `plugins/*`, and discovers those source-checkout plugin packages without symlinking them into `~/.pi-web/plugins`.
|
||||
The main PI WEB `dev` command watches bundled plugins in `pi-web-plugins/`, builds/watches separate plugin packages in `plugins/*`, and discovers those source-checkout plugin packages without symlinking them into `~/.pi-web/plugins`.
|
||||
|
||||
## Discovery and packaging
|
||||
|
||||
Pi Web builds `/pi-web-plugins/manifest.json` from these sources:
|
||||
PI WEB builds `/pi-web-plugins/manifest.json` from these sources:
|
||||
|
||||
1. Bundled plugins in the Pi Web package:
|
||||
1. Bundled plugins in the PI WEB package:
|
||||
|
||||
```text
|
||||
pi-web-plugins/<plugin-package>/
|
||||
@@ -166,7 +166,7 @@ Pi Web builds `/pi-web-plugins/manifest.json` from these sources:
|
||||
|
||||
Entries may be real directories or symlinks. This is the recommended development workflow.
|
||||
|
||||
3. Installed Pi packages that expose Pi Web plugin metadata. Pi packages may be user or project scoped.
|
||||
3. Installed Pi packages that expose PI WEB plugin metadata. Pi packages may be user or project scoped.
|
||||
|
||||
Plugin package directory names and plugin ids must be valid identifiers:
|
||||
|
||||
@@ -174,7 +174,7 @@ Plugin package directory names and plugin ids must be valid identifiers:
|
||||
^[a-z][a-z0-9.-]*$
|
||||
```
|
||||
|
||||
A package can expose one or more Pi Web plugin modules. There is exactly one supported `package.json` metadata shape:
|
||||
A package can expose one or more PI WEB plugin modules. There is exactly one supported `package.json` metadata shape:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -222,7 +222,7 @@ A plugin can fetch its own static assets with URLs under:
|
||||
/pi-web-plugins/<plugin-id>/<path-inside-plugin-root>
|
||||
```
|
||||
|
||||
Pi Web prevents asset path traversal outside the plugin root. JavaScript, JSON, CSS, and HTML get appropriate content types; other files are served as octet-stream.
|
||||
PI WEB prevents asset path traversal outside the plugin root. JavaScript, JSON, CSS, and HTML get appropriate content types; other files are served as octet-stream.
|
||||
|
||||
## Plugin module shape
|
||||
|
||||
@@ -264,7 +264,7 @@ export default {
|
||||
|
||||
`activate()` is called once when the UI loads the plugin. Keep it cheap: define contributions there, but move expensive or async work into actions, custom elements, or explicit user interactions.
|
||||
|
||||
The plugin id comes from `package.json`, not from the JavaScript module. Contribution ids are local to the plugin and Pi Web qualifies them internally as:
|
||||
The plugin id comes from `package.json`, not from the JavaScript module. Contribution ids are local to the plugin and PI WEB qualifies them internally as:
|
||||
|
||||
```text
|
||||
<plugin-id>:<local-contribution-id>
|
||||
@@ -345,17 +345,17 @@ Notes:
|
||||
|
||||
- `state` is a snapshot of current UI state when actions are built.
|
||||
- Only `state.selectedWorkspace` and `state.selectedSession` are documented as stable for plugin authors.
|
||||
- Other `state` fields may exist at runtime, but they are Pi Web internals and can change quickly.
|
||||
- Other `state` fields may exist at runtime, but they are PI WEB internals and can change quickly.
|
||||
- `enabled` is evaluated when the action palette asks for actions.
|
||||
- `selectWorkspaceTool()` expects a qualified panel id such as `my-plugin:workspace.info`.
|
||||
- `openTerminal()` switches to the built-in terminal panel. Pass `{ terminalId }` to deep-link to a specific terminal after creating one through the terminal API.
|
||||
|
||||
#### Keyboard shortcuts
|
||||
|
||||
- App-level keyboard shortcuts must be attached to actions. Pi Web does not support standalone plugin keyboard commands; contribute an action first, then add a `shortcut` if it needs a keybinding.
|
||||
- App-level keyboard shortcuts must be attached to actions. PI WEB does not support standalone plugin keyboard commands; contribute an action first, then add a `shortcut` if it needs a keybinding.
|
||||
- `shortcut` is the action's default keybinding. It is displayed in the action palette and handled by the global shortcut dispatcher when the action is enabled.
|
||||
- Use modified shortcuts such as `mod+shift+p`; plain letter shortcuts are intentionally ignored so normal typing is never captured.
|
||||
- Future Pi Web versions may allow users to override or disable action shortcuts by action id, so plugins should treat `shortcut` as a default rather than a guaranteed final binding.
|
||||
- Future PI WEB versions may allow users to override or disable action shortcuts by action id, so plugins should treat `shortcut` as a default rather than a guaranteed final binding.
|
||||
- Choose shortcuts carefully to avoid conflicts. There is no user-facing shortcut override or conflict resolver yet.
|
||||
- Local text input, terminal input, list navigation, and dialog keys such as Enter, Escape, and arrow keys do not need to be plugin actions unless they are app-level commands.
|
||||
|
||||
@@ -399,7 +399,7 @@ interface WorkspacePanelContext {
|
||||
}
|
||||
```
|
||||
|
||||
`workspace` and `openTerminal()` are documented as stable for panel callbacks. Other fields may exist at runtime, but they are Pi Web internals and can change quickly. Use `openTerminal({ terminalId })` when a panel creates a terminal and wants Pi Web to navigate to that specific terminal. If a panel needs file, git, or session data, prefer explicit `fetch()` calls and keep them isolated.
|
||||
`workspace` and `openTerminal()` are documented as stable for panel callbacks. Other fields may exist at runtime, but they are PI WEB internals and can change quickly. Use `openTerminal({ terminalId })` when a panel creates a terminal and wants PI WEB to navigate to that specific terminal. If a panel needs file, git, or session data, prefer explicit `fetch()` calls and keep them isolated.
|
||||
|
||||
Useful workspace shape:
|
||||
|
||||
@@ -420,7 +420,7 @@ Use existing classes such as `toolbar`, `viewer`, `empty`, and `muted` for panel
|
||||
|
||||
### Workspace labels
|
||||
|
||||
Workspace labels add compact inline metadata wherever Pi Web displays a workspace label: workspace list, workspace panel header, and status bar.
|
||||
Workspace labels add compact inline metadata wherever PI WEB displays a workspace label: workspace list, workspace panel header, and status bar.
|
||||
|
||||
Use them for short facts like project environment, local URL, branch status, container name, or health state.
|
||||
|
||||
@@ -456,7 +456,7 @@ interface WorkspaceLabelContext {
|
||||
}
|
||||
```
|
||||
|
||||
Only `workspace` is documented as stable for label callbacks. Other fields may exist at runtime, but they are Pi Web internals and can change quickly.
|
||||
Only `workspace` is documented as stable for label callbacks. Other fields may exist at runtime, but they are PI WEB internals and can change quickly.
|
||||
|
||||
Items are sorted by `order` and then id. Return an empty array to render nothing.
|
||||
|
||||
@@ -478,7 +478,7 @@ Items are sorted by `order` and then id. Return an empty array to render nothing
|
||||
}
|
||||
```
|
||||
|
||||
Pi Web renders the anchor and adds safe defaults such as `rel="noopener noreferrer"` for `_blank` links. `javascript:` and `data:` links are rendered as plain text instead of links.
|
||||
PI WEB renders the anchor and adds safe defaults such as `rel="noopener noreferrer"` for `_blank` links. `javascript:` and `data:` links are rendered as plain text instead of links.
|
||||
|
||||
#### Render items
|
||||
|
||||
@@ -518,7 +518,7 @@ export default {
|
||||
|
||||
## Reading workspace files
|
||||
|
||||
Plugins can use existing Pi Web endpoints. For example, to read a file in a workspace:
|
||||
Plugins can use existing PI WEB endpoints. For example, to read a file in a workspace:
|
||||
|
||||
```js
|
||||
async function readWorkspaceFile(workspace, path) {
|
||||
@@ -533,13 +533,13 @@ async function readWorkspaceFile(workspace, path) {
|
||||
}
|
||||
```
|
||||
|
||||
The file response includes fields such as `path`, `content`, `truncated`, and `binary`, but endpoint response shapes are private Pi Web implementation details for now and can change between releases.
|
||||
The file response includes fields such as `path`, `content`, `truncated`, and `binary`, but endpoint response shapes are private PI WEB implementation details for now and can change between releases.
|
||||
|
||||
Be careful with sensitive files such as `.env`: plugins are trusted browser code, and file contents are exposed to the plugin.
|
||||
|
||||
## Other useful Pi Web APIs
|
||||
## Other useful PI WEB APIs
|
||||
|
||||
Plugins may call any endpoint available to the browser, but these HTTP endpoints are considered private Pi Web implementation APIs for now. They can change quickly between releases. Prefer plugin runtime context helpers when they cover the interaction, and keep any direct HTTP usage small and isolated.
|
||||
Plugins may call any endpoint available to the browser, but these HTTP endpoints are considered private PI WEB implementation APIs for now. They can change quickly between releases. Prefer plugin runtime context helpers when they cover the interaction, and keep any direct HTTP usage small and isolated.
|
||||
|
||||
Common read endpoints:
|
||||
|
||||
@@ -566,11 +566,11 @@ POST /api/sessions/:id/archive
|
||||
POST /api/sessions/:id/restore
|
||||
```
|
||||
|
||||
Prefer runtime context helpers (`startSession`, `stopActiveWork`, `refreshFiles`, `refreshGit`, etc.) when they cover the interaction. Use direct HTTP calls only for plugin-specific data or behavior, and expect to update them as Pi Web evolves.
|
||||
Prefer runtime context helpers (`startSession`, `stopActiveWork`, `refreshFiles`, `refreshGit`, etc.) when they cover the interaction. Use direct HTTP calls only for plugin-specific data or behavior, and expect to update them as PI WEB evolves.
|
||||
|
||||
## Async data and caching
|
||||
|
||||
Pi Web does not provide a plugin cache/invalidation framework. Keep host callbacks cheap:
|
||||
PI WEB does not provide a plugin cache/invalidation framework. Keep host callbacks cheap:
|
||||
|
||||
- simple contributions should be synchronous and cheap;
|
||||
- expensive or async work should live inside the plugin;
|
||||
@@ -580,7 +580,7 @@ Pi Web does not provide a plugin cache/invalidation framework. Keep host callbac
|
||||
|
||||
## Agent implementation checklist
|
||||
|
||||
If you are an AI agent building or editing a Pi Web plugin, follow this checklist:
|
||||
If you are an AI agent building or editing a PI WEB plugin, follow this checklist:
|
||||
|
||||
1. Create or update a plugin folder with `package.json` and a JavaScript module such as `pi-web-plugin.js`.
|
||||
2. Use the single supported package metadata shape: `piWeb.plugins` array with `{ id, module }` entries.
|
||||
@@ -594,7 +594,7 @@ If you are an AI agent building or editing a Pi Web plugin, follow this checklis
|
||||
10. Add workspace labels for compact inline metadata.
|
||||
11. Return arrays from workspace label `items()`; return an empty array to render nothing.
|
||||
12. Use stable context fields first; only `workspace`, `state.selectedWorkspace`, and `state.selectedSession` are documented as stable.
|
||||
13. Use `fetch()` against Pi Web APIs only for plugin-specific behavior not provided by runtime context helpers, and isolate those calls because HTTP endpoints are private for now.
|
||||
13. Use `fetch()` against PI WEB APIs only for plugin-specific behavior not provided by runtime context helpers, and isolate those calls because HTTP endpoints are private for now.
|
||||
14. Treat plugins as trusted code and avoid reading or displaying secrets unless intentional.
|
||||
15. After local edits, tell the user to hard reload the browser and check the console for plugin errors.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
<title>Remote-first development with PI WEB</title>
|
||||
<meta
|
||||
name="description"
|
||||
content="Why Pi Web is built for remote AI-driven development with persistent agents and browser-based control."
|
||||
content="Why PI WEB is built for remote AI-driven development with persistent agents and browser-based control."
|
||||
/>
|
||||
<meta property="og:title" content="Remote-first development with PI WEB" />
|
||||
<meta property="og:image" content="assets/pi-web-banner.png" />
|
||||
@@ -28,13 +28,13 @@
|
||||
<body>
|
||||
<header class="site-header">
|
||||
<nav class="container nav" aria-label="Main navigation">
|
||||
<a class="brand" href="./" aria-label="Pi Web home">Pi Web</a>
|
||||
<a class="brand" href="./" aria-label="PI WEB home">PI WEB</a>
|
||||
<div class="nav-links">
|
||||
<a href="remote-first.html" aria-current="page">Remote-first</a>
|
||||
<a href="install.html">Install</a>
|
||||
<a href="plugins.html">Plugins</a>
|
||||
<a href="faq.html">FAQ</a>
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="Pi Web on GitHub">
|
||||
<a class="github-link" href="https://github.com/jmfederico/pi-web" aria-label="PI WEB on GitHub">
|
||||
<svg class="github-icon" viewBox="0 0 16 16" aria-hidden="true">
|
||||
<path
|
||||
fill="currentColor"
|
||||
@@ -57,7 +57,7 @@
|
||||
<p class="eyebrow"><span class="pulse"></span> Remote-first development</p>
|
||||
<h1>Your laptop is a window, not the workstation.</h1>
|
||||
<p>
|
||||
Pi Web is built around a simple shift: development should live where the work happens, not where your
|
||||
PI WEB is built around a simple shift: development should live where the work happens, not where your
|
||||
current keyboard happens to be.
|
||||
</p>
|
||||
</div>
|
||||
@@ -116,7 +116,7 @@
|
||||
<section id="browser-control">
|
||||
<h2>The browser becomes the control plane</h2>
|
||||
<p>
|
||||
Your device should not have to be the editor, terminal, build server, and agent runtime. In Pi Web, the
|
||||
Your device should not have to be the editor, terminal, build server, and agent runtime. In PI WEB, the
|
||||
browser is the cockpit: supervise sessions, redirect agents, inspect transcripts, and review progress
|
||||
while the development environment stays remote and stable.
|
||||
</p>
|
||||
@@ -137,7 +137,7 @@
|
||||
<section id="recommended-shape">
|
||||
<h2>Recommended shape</h2>
|
||||
<p>
|
||||
Pi Web works locally, but it shines on a machine that stays on and is reachable through a private path:
|
||||
PI WEB works locally, but it shines on a machine that stays on and is reachable through a private path:
|
||||
SSH tunnel, VPN, private LAN, or an authenticated reverse proxy.
|
||||
</p>
|
||||
<div class="callout warning">
|
||||
@@ -145,7 +145,7 @@
|
||||
keep working even when the laptop is gone.
|
||||
</div>
|
||||
<div class="doc-actions">
|
||||
<a class="button primary" href="install.html">Install Pi Web</a>
|
||||
<a class="button primary" href="install.html">Install PI WEB</a>
|
||||
<a class="button" href="faq.html#laptop-or-server">Laptop or server FAQ</a>
|
||||
</div>
|
||||
</section>
|
||||
@@ -156,7 +156,7 @@
|
||||
|
||||
<footer class="site-footer">
|
||||
<div class="container footer-inner">
|
||||
<span>Pi Web · remote-first control for persistent AI agents.</span>
|
||||
<span>PI WEB · remote-first control for persistent AI agents.</span>
|
||||
<div class="footer-links">
|
||||
<a href="./">Home</a>
|
||||
<a href="install.html">Install</a>
|
||||
|
||||
Reference in New Issue
Block a user