mirror of
https://github.com/PerpetualSoftware/pad.git
synced 2026-09-22 18:43:45 +00:00
de8679f535
* chore(mcp): bump ToolSurfaceVersion 0.3 → 0.4; document v0.4 envelope (TASK-1418)
Final PR of PLAN-1410. The contractual announcement that the v0.4
bootstrap shape is stable.
## What
1. internal/mcp/version.go — ToolSurfaceVersion: "0.3" → "0.4".
The godoc on the constant gains a full v0.4 changelog entry
enumerating each shape change shipped by PLAN-1410's six
bootstrap PRs:
- BootstrapCollection projection (TASK-1412): drops id,
workspace_id, created_at, updated_at, settings; schema as
a nested JSON object.
- BootstrapRole projection (TASK-1423): drops id,
workspace_id, tools, created_at, updated_at.
- Convention slug dropped (TASK-1413).
- Top-level recent_activity duplicate removed (TASK-1413).
- BootstrapDashboard wrapper caps five sub-arrays (TASK-1413
+ TASK-1422): attention, recent_activity, active_items,
active_plans, by_role at 5 entries each, parallel
*_overflow_count fields. suggested_next deliberately
excluded — already capped to 3 upstream.
- Schema label omitted when label == TitleCase(key) (TASK-1424).
Plus an explicit compatibility note: all v0.4 changes are
additive or subtractive (no field renames); clients that read
the preserved field names keep working unchanged.
2. CLAUDE.md updates:
- "## MCP server" header: v0.3 catalog → v0.4 catalog, with a
one-paragraph summary of what v0.4 shipped.
- "Surface:" Tools bullet: v0.3 → v0.4, with a note that the
tool/action surface is unchanged — only the bootstrap JSON
these tools return has been trimmed.
- "Stability contract": ToolSurfaceVersion (currently "0.4"),
comprehensive single-paragraph description of the v0.4
envelope, cumulative size reduction (40% live / 54% fixture),
and explicit additive/subtractive note.
## Why the strategy worked
PLAN-1410's "version bump last" strategy paid off:
- Each individual shape PR (TASK-1412/1413/1422/1423/1424) was
reviewable in isolation against a stable v0.3 contract.
- The six skill-side PRs (TASK-1414/1415/1416) had no MCP-shape
impact and didn't need any version bump consideration.
- v0.4 is now announced as a single comprehensive contract change,
not five separate version bumps — easier for downstream MCP
consumers (Claude Desktop, Cursor, future Pad Cloud remote MCP)
to reason about.
## Verification
- `make check` — golangci-lint 0 issues, all Go tests pass
(including the version-tracking tests in catalog_meta_test.go
that auto-pin to whatever ToolSurfaceVersion is set to),
govulncheck clean, web build clean.
- MCP handshake (verified via `pad mcp serve` + an initialize
JSON-RPC request) advertises
capabilities.experimental.padToolSurface.version = "0.4".
padCmdhelp.version stays at "0.1" as expected.
## Post-merge follow-ups
After this lands:
- Update PLAN-1410's Result section with a "v0.4 announced" line
and the final post-everything measurement (taken against
docapp after `make install`).
- Flip PLAN-1410 status from `active` → `completed`.
These are pad-item operations, not git changes.
Parent: PLAN-1410. Closes the plan.
* fix(mcp): update stale v0.3 references after ToolSurfaceVersion bump (TASK-1418 follow-up)
Address Codex P2 + P3 findings on PR #544: bumping
ToolSurfaceVersion in version.go left four runtime/user-facing
docs still claiming v0.3:
P2 — runtime MCP docs:
- internal/mcp/instructions.md "## Tool surface (v0.3)" → v0.4
- internal/mcp/catalog_meta.go "v0.3 server-introspection tool" → "(v0.4 catalog)"
- internal/mcp/catalog_meta.go padMetaToolDescription twice:
* "the v0.3 tool catalog" → "the v0.4 tool catalog"
* "v0.3 catalog dump" → "v0.4 catalog dump"
- internal/mcp/catalog_meta.go actionMetaToolSurface godoc:
"v0.3 catalog" → "catalog" (de-versioned; the comment is
about scope, not version)
P3 — public README:
- README.md "Tool catalog (v0.3)" → "Tool catalog (v0.4)"
- README.md "tool_surface_version: '0.3'" → "'0.4'" with a
pointer to PLAN-1410's bootstrap-trim summary and
version.go's full v0.4 changelog.
Without these, agents reading the initialize-instructions blob or
pad_meta's tool description (both of which are part of the
runtime MCP surface, not just internal docs) would see v0.3 while
the handshake / pad_meta.action: version returned v0.4 — the
exact "contradictory metadata depending on what you read" failure
mode Codex flagged.
Same skill-↔-code sync pattern that has been a running theme
through PLAN-1410's review loops. The cluster of stale references
is a classic side effect of a version bump landing late in a
plan — the version constant is one string, but downstream prose
that names it lives in multiple places.
Verified no remaining "v0.3" claims that imply currency — `grep -rn
"v0\.3\|tool_surface_version" --include="*.{go,md}"` returns only
historical-context mentions in changelog godocs (correct) and the
runtime constant readback (correctly returns "0.4" now).
Parent: PLAN-1410 / TASK-1418.
* fix(mcp): correct schema-type-change disclosure + stale cmdhelp-walker description (TASK-1418 follow-up)
Address Codex round 2 P3 findings on PR #544:
## P3 — `cmd/pad/mcp.go` still described the retired leaf walker
The `pad mcp serve` command's Long description said "every leaf
command becomes an MCP tool, except the curated allow-list
exclusions" — that was true under v0.1 but the cmdhelp leaf
walker was retired in TASK-981 (PLAN-969's v0.2 rollout). The
v0.2/v0.3/v0.4 surface has always been the hand-curated catalog
of eight resource × action tools + pad_set_workspace.
Updated the Long description to:
- Name the v0.4 catalog explicitly.
- List the eight resource × action tools.
- Note that cmdhelp v0.1 still drives per-command arg schemas
at dispatch time (so it's not gone, just no longer drives
tool naming/count).
- Reference TASK-981 for the cutover.
## P3 — "additive/subtractive only" was misleading
The compatibility note in `version.go` and `CLAUDE.md` claimed
all v0.4 changes were additive or subtractive. That glossed over
one breaking change in TASK-1412: `collections[].schema` went
from a JSON-encoded string ("schema":"{\"fields\":...}") to a
nested JSON object ("schema":{"fields":...}). For any v0.3
consumer that read schema as a string and JSON.parse()'d it
themselves, that's a TYPE change, not a no-op.
Updated both godoc and CLAUDE.md to explicitly call this out
as the one breaking change, separately from the additive/
subtractive bucket. Better for downstream MCP consumers to see
the truth than to discover it via runtime failure.
The remaining v0.4 changes ARE additive (overflow counts on
BootstrapDashboard) or subtractive (dropped fields with named
canonical alternatives) — those parts of the original note
are accurate and kept.
Honesty about compatibility is more valuable than a tidy
narrative. Surfaced explicitly in the godoc + the public
contract doc; PLAN-1410's Result section was already honest
about the field-level deltas.
Parent: PLAN-1410 / TASK-1418.
427 lines
20 KiB
Markdown
427 lines
20 KiB
Markdown
<p align="center">
|
||
<h1 align="center">Pad</h1>
|
||
<p align="center"><strong>Project Management for the agent era.</strong></p>
|
||
<p align="center">
|
||
<a href="https://github.com/PerpetualSoftware/pad/actions/workflows/ci.yml"><img src="https://github.com/PerpetualSoftware/pad/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
|
||
<a href="https://github.com/PerpetualSoftware/pad/releases"><img src="https://img.shields.io/github/v/release/PerpetualSoftware/pad" alt="Release"></a>
|
||
<a href="https://goreportcard.com/report/github.com/PerpetualSoftware/pad"><img src="https://goreportcard.com/badge/github.com/PerpetualSoftware/pad" alt="Go Report Card"></a>
|
||
<a href="https://github.com/PerpetualSoftware/pad/pkgs/container/pad"><img src="https://img.shields.io/badge/ghcr.io-perpetualsoftware%2Fpad-blue?logo=docker&logoColor=white" alt="Container image on GHCR"></a>
|
||
<a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-blue" alt="License"></a>
|
||
<a href="https://github.com/sponsors/xarmian"><img src="https://img.shields.io/github/sponsors/xarmian?label=sponsors&logo=github" alt="GitHub Sponsors"></a>
|
||
</p>
|
||
</p>
|
||
|
||
---
|
||
|
||
> One binary. Local-first. No accounts required. Pad gives you a CLI, a web UI, and an AI agent skill — all backed by SQLite, all running on your machine. Your project data never leaves your laptop.
|
||
|
||
<p align="center">
|
||
<img src="docs/screenshots/dashboard.png" width="900" alt="Pad dashboard showing collection summaries, active work, an active plan with progress, and a recent activity feed" />
|
||
</p>
|
||
|
||
## Quick Start
|
||
|
||
```bash
|
||
brew install PerpetualSoftware/tap/pad
|
||
cd your-project
|
||
pad init # configure, auth, workspace, AI skill — all in one
|
||
pad server open # opens the web UI at localhost:7777
|
||
```
|
||
|
||
`pad init` is the smart entry point — it auto-detects what's needed, walks you through each step, and is safe to re-run anytime (it skips finished steps and prints a status summary).
|
||
|
||
Then, in a fresh agent session in your project, say:
|
||
|
||
```
|
||
use pad to get IDEA-1
|
||
```
|
||
|
||
Your new workspace ships with a thoughtful first idea — IDEA-1 — that the agent reads and uses to help you get set up around your actual project. It's the fastest way to go from empty workspace to "okay, this is mine."
|
||
|
||
## Why Pad?
|
||
|
||
Tools like Linear, Jira, and Notion are built for teams on the cloud. Pad is built for **developers on their machine** — and for the AI agents working alongside them.
|
||
|
||
| | Pad | Linear / Jira | Notion |
|
||
|---|---|---|---|
|
||
| **Setup** | `pad init` | Create account, invite team, configure | Create account, pick template |
|
||
| **AI agents** | Native `/pad` skill for 7+ tools | Third-party integrations | Third-party integrations |
|
||
| **Data** | Local SQLite, you own it | Their cloud | Their cloud |
|
||
| **Offline** | Full functionality | Read-only cache at best | Limited |
|
||
| **CLI** | First-class | Afterthought | None |
|
||
| **Price** | Free, open source | Per-seat pricing | Per-seat pricing |
|
||
|
||
## Features
|
||
|
||
### For Developers
|
||
|
||
**CLI that doesn't get in your way.** Create tasks, search items, check status — without leaving the terminal.
|
||
|
||
```bash
|
||
pad item create task "Fix OAuth redirect" --priority high
|
||
pad item create idea "Real-time collaboration" --category infrastructure
|
||
pad item list tasks --status in-progress
|
||
pad item search "authentication"
|
||
pad project dashboard # Project dashboard
|
||
pad project next # What should I work on?
|
||
pad server info # How this client is connected to Pad
|
||
```
|
||
|
||
**Web UI that stays out of your way.** A clean, dark-themed interface at `localhost:7777` with:
|
||
|
||
- **Board, list, and table views** — drag-and-drop between status columns
|
||
- **Keyboard navigation** — `j`/`k` to move, `Enter` to open, `Esc` to go back, `Cmd+K` to search
|
||
- **Rich text editor** — Tiptap-based with markdown, formatting toolbar, and auto-save
|
||
- **Wiki-links** — type `[[Title]]` to link between items
|
||
- **Real-time updates** — agent creates a task in the terminal, it appears in the browser instantly (via SSE)
|
||
- **Dashboard** — collection overview, active work, plan tracking, activity feed
|
||
|
||
<p align="center">
|
||
<img src="docs/screenshots/board.png" width="900" alt="Pad tasks board view: kanban columns for Open, In-Progress, Done, Cancelled with task cards in each" />
|
||
</p>
|
||
|
||
### For AI Agents
|
||
|
||
**Your agent becomes a project partner.** Install the `/pad` skill once, and your AI coding tool can read, create, and update project items through natural language.
|
||
|
||
```bash
|
||
pad agent install # Auto-detects your tools and installs the skill
|
||
```
|
||
|
||
Works with **Claude Code**, **Cursor**, **Windsurf**, **Codex**, **GitHub Copilot**, **Amazon Q**, and **JetBrains Junie**.
|
||
|
||
Then just talk to your project:
|
||
|
||
```
|
||
> /pad what should I work on next?
|
||
> /pad I finished the OAuth fix
|
||
> /pad create a task to add rate limiting
|
||
> /pad let's brainstorm about the API redesign
|
||
```
|
||
|
||
**Conventions and playbooks** teach agents how your project works:
|
||
|
||
- **Conventions** — trigger-based rules like "run tests before marking a task done" or "use conventional commits"
|
||
- **Playbooks** — multi-step workflows like "when implementing a feature: read the spec, create a branch, write tests first, then implement". Playbooks can declare a kebab-case `invocation_slug` so users can invoke them directly: `/pad ship PLAN-42`, `/pad release 0.5.0`. Fresh `startup` workspaces ship a generic `ship` playbook out of the box.
|
||
|
||
```bash
|
||
pad item create convention "Run tests before completing tasks" \
|
||
--field trigger=on-task-complete \
|
||
--field scope=all \
|
||
--field priority=must
|
||
```
|
||
|
||
Agents load relevant conventions automatically. All agent actions are attributed in the activity feed, so you always know what the AI changed.
|
||
|
||
**Onboard agents to a new codebase:**
|
||
|
||
```bash
|
||
pad workspace onboard # Analyzes project structure, saves workspace context, and suggests conventions
|
||
```
|
||
|
||
### Collections & Custom Fields
|
||
|
||
Pad organizes work into **collections** — typed containers with structured fields.
|
||
|
||
**Built-in collections:**
|
||
|
||
| Collection | Purpose |
|
||
|---|---|
|
||
| **Tasks** | Work items with status, priority, assignee, effort, due date |
|
||
| **Ideas** | Feature ideas with impact and category |
|
||
| **Plans** | Project milestones with progress tracking |
|
||
| **Docs** | Documentation, decisions, reference material |
|
||
| **Conventions** | Project rules that guide agent behavior |
|
||
| **Playbooks** | Multi-step workflows for agents to follow |
|
||
|
||
**Create your own** with typed fields — select, text, date, number, url, relation, checkbox:
|
||
|
||
```bash
|
||
pad collection create "Bug Reports" \
|
||
--fields "severity:select:low,medium,high,critical; browser:text; reproducible:checkbox"
|
||
```
|
||
|
||
Items get reference numbers automatically (`TASK-5`, `BUG-12`) and can be moved between collections with field migration.
|
||
|
||
## Installation
|
||
|
||
### Homebrew (macOS and Linux)
|
||
|
||
```bash
|
||
brew install PerpetualSoftware/tap/pad
|
||
```
|
||
|
||
### Build from Source
|
||
|
||
```bash
|
||
git clone https://github.com/PerpetualSoftware/pad
|
||
cd pad
|
||
make build
|
||
cp pad ~/.local/bin/ # or /usr/local/bin/
|
||
```
|
||
|
||
Requires Go 1.26+ and Node.js 22+.
|
||
|
||
The `go install github.com/PerpetualSoftware/pad/cmd/pad@latest` path is not supported for the full Pad binary, because the web UI must be built and embedded during the source build.
|
||
|
||
### Docker
|
||
|
||
```bash
|
||
docker run -p 127.0.0.1:7777:7777 -v pad-data:/data ghcr.io/perpetualsoftware/pad
|
||
```
|
||
|
||
This publishes Pad to `localhost:7777` on the host machine, which is the recommended default for local use.
|
||
|
||
**Single user, more than one device?** Publish to all interfaces so you can reach Pad from your phone, tablet, or another machine on the same LAN, Tailscale network, or home VPN:
|
||
|
||
```bash
|
||
docker run -p 7777:7777 -v pad-data:/data ghcr.io/perpetualsoftware/pad
|
||
```
|
||
|
||
For multi-instance deployments, Pad supports Postgres + Redis via `docker-compose.yml` — see [docs/deployment.md](docs/deployment.md) for the full setup.
|
||
|
||
### Binary Download
|
||
|
||
Pre-built binaries for macOS, Linux, and Windows are available on the [releases page](https://github.com/PerpetualSoftware/pad/releases).
|
||
|
||
## Getting Started
|
||
|
||
### 1. Set up Pad
|
||
|
||
```bash
|
||
cd ~/projects/myapp
|
||
pad init "My App"
|
||
```
|
||
|
||
`pad init` is the smart entry point that handles everything in one command:
|
||
|
||
- Configures this client's connection (local server, remote, or Docker)
|
||
- Auto-starts the local server
|
||
- Creates the first admin account on a fresh local install (Docker / remote hosts run `pad auth setup` on the server instead)
|
||
- Logs you in if needed
|
||
- Creates or links a workspace for the current directory (writes `.pad.toml`)
|
||
- Installs the `/pad` skill for any AI tools detected in the project
|
||
|
||
Run from your project root. Safe to re-run anytime — it skips finished steps and prints a status summary if nothing's needed.
|
||
|
||
**Choose a template** with `--template`, or omit it for an interactive picker grouped by category (Software / People / …):
|
||
|
||
```bash
|
||
pad workspace init --list-templates # See the full catalog grouped by category
|
||
pad init "My App" --template scrum # Scrum-style with sprints
|
||
pad init "My App" --template product # Product management focused
|
||
pad init "My Hiring" --template hiring # Company-side: requisitions, candidates, interview loops, feedback
|
||
pad init "Job Search" --template interviewing # Candidate-side: applications, interviews, companies, contacts
|
||
```
|
||
|
||
Pad ships templates for software (startup / scrum / product), people workflows (hiring, interviewing), and has reserved categories for research, content, operations, and personal use so the same project-management primitives fit well beyond code projects.
|
||
|
||
### 2. Start working
|
||
|
||
```bash
|
||
# From the CLI
|
||
pad item create task "Set up CI pipeline" --priority high
|
||
pad item create idea "Add WebSocket support" --category infrastructure
|
||
pad project dashboard
|
||
|
||
# From the web UI
|
||
pad server open # Opens localhost:7777 in your browser
|
||
|
||
# From your AI agent
|
||
# Just use /pad in Claude Code, Cursor, etc.
|
||
```
|
||
|
||
### 3. Teach your agents the rules
|
||
|
||
```bash
|
||
pad workspace onboard # Auto-analyze project, save workspace context, and suggest conventions
|
||
# Or browse the convention library
|
||
pad library list --type conventions # Pre-built conventions you can adopt
|
||
pad library list --type playbooks # Pre-built multi-step workflows
|
||
```
|
||
|
||
### 4. Optional — connect a desktop AI app via MCP
|
||
|
||
Pad ships an MCP (Model Context Protocol) server so Claude Desktop, Cursor, or
|
||
Windsurf can manage items, plans, ideas, and dependencies as native tools, read
|
||
workspace state by URL, and load multi-step workflows as prompts.
|
||
|
||
```bash
|
||
pad mcp install claude-desktop # or: cursor, windsurf, --all
|
||
# Restart the client; pad shows up as the "pad" MCP server.
|
||
```
|
||
|
||
**Tool catalog (v0.4)** — eight resource × action tools plus `pad_set_workspace` (nine total), no flat verb explosion:
|
||
|
||
| Tool | Actions |
|
||
|---|---|
|
||
| `pad_item` | `create`, `update`, `delete`, `get`, `list`, `move`, `link`, `unlink`, `deps`, `star`, `unstar`, `starred`, `comment`, `list-comments`, `bulk-update`, `note`, `decide` |
|
||
| `pad_workspace` | `list`, `members`, `invite`, `storage`, `audit-log` |
|
||
| `pad_collection` | `list`, `create` |
|
||
| `pad_project` | `dashboard`, `next`, `standup`, `changelog` |
|
||
| `pad_role` | `list`, `create`, `delete` |
|
||
| `pad_search` | `query` |
|
||
| `pad_playbook` | `list`, `get`, `run` |
|
||
| `pad_meta` | `server-info`, `version`, `tool-surface`, `bootstrap` |
|
||
| `pad_set_workspace` | session-default workspace pinning (response embeds the bootstrap blob) |
|
||
|
||
Plus resources at `pad://workspaces`, `pad://workspace/{ws}/dashboard`,
|
||
`pad://workspace/{ws}/items`, `pad://workspace/{ws}/items/{ref}`,
|
||
`pad://workspace/{ws}/collections`, `pad://workspace/{ws}/bootstrap`,
|
||
and `pad://_meta/version`.
|
||
|
||
**Stability contract** — two version constants, both advertised in the
|
||
initialize handshake under `capabilities.experimental.padCmdhelp` and
|
||
`capabilities.experimental.padToolSurface` (and queryable at
|
||
`pad://_meta/version`):
|
||
|
||
- `cmdhelp_version: "0.1"` — CLI help-tree contract (used at dispatch time)
|
||
- `tool_surface_version: "0.4"` — MCP tool catalog contract (PLAN-1410 trimmed the bootstrap-response shape by ~40%; see `internal/mcp/version.go` for the full v0.4 changelog)
|
||
|
||
External agents pin against these so a future rename doesn't break them
|
||
silently. Errors come back as structured envelopes (`{error: {code,
|
||
message, hint, available_workspaces, ...}}`) with a closed eight-code
|
||
taxonomy.
|
||
|
||
Full guide at [getpad.dev/mcp/local](https://getpad.dev/mcp/local) — install
|
||
paths, action enums per tool, error taxonomy, troubleshooting.
|
||
|
||
## CLI Reference
|
||
|
||
```
|
||
pad auth configure Configure how this client connects to Pad
|
||
pad auth setup Initialize the first admin account
|
||
pad auth login Sign in
|
||
pad auth whoami Show current user
|
||
|
||
pad server start Start the Pad API server
|
||
pad server stop Stop the Pad server
|
||
pad server info Show client, connection, and local server status
|
||
pad server open Open web UI in browser
|
||
|
||
pad workspace init [name] Initialize workspace in current directory
|
||
pad workspace link <workspace> Link current directory to an existing workspace
|
||
pad workspace list List all workspaces
|
||
pad workspace switch <workspace> Switch active workspace
|
||
pad workspace context Show structured workspace context
|
||
pad workspace context set --file X Update structured workspace context from JSON
|
||
pad workspace onboard Analyze project, save workspace context, and suggest conventions
|
||
pad workspace members List workspace members
|
||
pad workspace invite <email> Invite a workspace member
|
||
pad workspace join <code> Accept an invitation
|
||
pad workspace export Export workspace data
|
||
pad workspace import <file> Import workspace data
|
||
|
||
pad project dashboard Project dashboard
|
||
pad project next Recommended next task
|
||
pad project ready Query actionable next items
|
||
pad project stale Query stalled or attention-worthy items
|
||
pad project standup [--days N] Daily standup report
|
||
pad project changelog [--days N] Release notes from completed items
|
||
pad project watch Real-time activity stream
|
||
pad project reconcile Reconcile item and PR state
|
||
|
||
pad item create <coll> "title" Create item (task, idea, plan, doc, ...)
|
||
pad item list [collection] List items (filters: --status, --priority, --all)
|
||
pad item show <ref> Show item detail
|
||
pad item update <ref> Update item fields
|
||
pad item delete <ref> Delete item
|
||
pad item move <ref> <collection> Move item between collections
|
||
pad item edit <ref> Open item in $EDITOR
|
||
pad item search "query" Full-text search across all items
|
||
pad item comment <ref> "text" Add comment to an item
|
||
pad item comments <ref> View item comments
|
||
pad item note <ref> "summary" Append an implementation note to an item
|
||
pad item decide <ref> "decision" Append a decision log entry to an item
|
||
pad item block <src> <target> Create dependency
|
||
pad item blocked-by <item> <blk> Mark item as blocked
|
||
pad item deps <ref> Show dependencies
|
||
pad item unblock <src> <target> Remove dependency
|
||
pad item related <ref> Show direct relationships for an item
|
||
pad item implemented-by <ref> Show incoming implementers for an item
|
||
pad item bulk-update --status X Batch update multiple items
|
||
|
||
pad collection list List collections with item counts
|
||
pad collection create <name> Create a custom collection
|
||
|
||
pad library list Browse convention and playbook library
|
||
pad library activate <title> Activate a convention or playbook
|
||
|
||
pad agent install [tool] Install /pad skill for AI coding tools
|
||
pad agent status Show supported tools and installation status
|
||
pad agent update Update installed tool integrations
|
||
|
||
pad github link [item-ref] Link current branch's PR to item
|
||
pad github status [item-ref] Show PR status for linked items
|
||
pad github unlink <item-ref> Remove PR link from item
|
||
|
||
pad webhook list List workspace webhooks
|
||
pad webhook create <url> Create webhook
|
||
```
|
||
|
||
All commands accept `--format json` for machine-readable output and `--workspace` to target a specific workspace.
|
||
|
||
### Authentication
|
||
|
||
Pad runs without authentication by default for frictionless local use. For local installs, `pad init` creates the first admin account inline. The lower-level commands are useful when you're hosting a Pad server (Docker / remote) and need to set up auth on the server host directly:
|
||
|
||
```bash
|
||
pad auth setup # Initialize the first admin account (server host, non-local mode)
|
||
pad auth login # Sign in
|
||
pad auth whoami # Show current user
|
||
pad auth logout # Sign out
|
||
```
|
||
|
||
Once a user exists, all API requests and web UI access require authentication. Credentials are stored in `~/.pad/credentials.json`. Multiple users can be invited to workspaces with role-based access control (`owner`, `editor`, `viewer`).
|
||
|
||
```bash
|
||
pad workspace members # List workspace members
|
||
pad workspace invite user@example.com
|
||
pad workspace join <code>
|
||
```
|
||
|
||
## Architecture
|
||
|
||
```
|
||
┌──────────────────────────────────────────────┐
|
||
│ pad (single binary) │
|
||
│ │
|
||
│ ┌──────────┐ ┌──────────┐ ┌────────────┐ │
|
||
│ │ CLI │ │ REST │ │ Embedded │ │
|
||
│ │ (Cobra) │ │ API │ │ Web UI │ │
|
||
│ └────┬─────┘ └────┬─────┘ │ (SvelteKit)│ │
|
||
│ │ HTTP │ └────────────┘ │
|
||
│ └──────────────┤ │
|
||
│ ┌─────▼─────┐ │
|
||
│ │ SQLite │ │
|
||
│ │ + FTS5 │ │
|
||
│ └───────────┘ │
|
||
└───────────────────────────────────────────────┘
|
||
```
|
||
|
||
- **Go backend** — chi router, SQLite via [modernc.org/sqlite](https://pkg.go.dev/modernc.org/sqlite) (pure Go, no CGO), FTS5 full-text search, SSE for real-time updates
|
||
- **SvelteKit frontend** — Svelte 5, Tiptap editor, drag-and-drop, adapter-static, embedded via `go:embed`
|
||
- **Single binary** — serves the API and web UI, runs on macOS, Linux, and Windows
|
||
- **Workspace-per-project** — each project gets its own workspace linked by a `.pad.toml` file
|
||
|
||
All data lives in `~/.pad/pad.db`. Your data. Your machine. No telemetry, no cloud, no accounts required.
|
||
|
||
## Contributing
|
||
|
||
See [CONTRIBUTING.md](CONTRIBUTING.md) for the development guide.
|
||
|
||
```bash
|
||
make build # Build web UI + Go binary
|
||
make test # Run Go tests
|
||
make dev-web # SvelteKit dev server with hot reload
|
||
make install # Build, install to ~/.local/bin, restart server
|
||
```
|
||
|
||
## Security
|
||
|
||
See [SECURITY.md](SECURITY.md) for reporting vulnerabilities.
|
||
|
||
## License
|
||
|
||
[Apache License 2.0](LICENSE)
|