The Agent Pipeline Tracker is a self-contained, browser-native HTML dashboard — no server, no Node.js proxy, no database required. Every agent record is persisted either in browser localStorage (instant, always available) or to a JSON file on SharePoint via the SP REST API (production mode for team-shared state).

The tracker was built to answer the question every MSP automation program runs into: "What agents do we have, where are they, who owns them, and when are they expected to hand off to the next stage?" That answer lives here, visible to anyone with access to the SharePoint page.

Audience: ITE Team leads, consultants, account managers, and executive stakeholders via the print report. Technicians use the Handoff column to know when new work items are landing on their plate.

Current state: Fully functional. localStorage mode works in any browser without configuration. SharePoint persistence mode requires one line of config (SP_SITE) and the target folder to exist in SharePoint. The print report generates a professional PDF-ready status report with branding, RAG status, risk dashboard, and milestone timeline.

Unlike the rest of the platform suite, the Agent Tracker requires no Node.js proxy. It uses two complementary persistence paths: localStorage for always-available fallback, and the SharePoint REST API directly from the browser for production team-shared state.

The SharePoint REST API is accessible from within a SharePoint ASPX page context because the browser is already authenticated as the logged-in user. The X-RequestDigest token is fetched from /_api/contextinfo and passed with every write operation.

Each agent is a plain JavaScript object. The full shape is documented below. All fields except name are optional — the tracker degrades gracefully when fields are missing.

Six summary cards sit at the top of the dashboard. They are computed from the agents[] array each time renderSummary() is called — which fires on every save, delete, phase change, and initial load.

The toolbar sits between the summary cards and the main view. All controls are in a single row. Left to right: Add Agent, view toggle (Table / Board), SharePoint status dot, phase filter dropdown, search input, agent count, Export button, Print button.

The Edit Claim button is a lightweight session-scoped editing signal designed to mitigate the last-write-wins limitation of the shared SharePoint JSON file. It does not block saves or prevent anyone from editing — it is a social convention that tells teammates "I am actively editing right now."

The button sits in the toolbar immediately to the right of the SharePoint status dot. It uses sessionStorage — not localStorage — so the claim automatically clears the moment the browser tab is closed or the browser is quit. No stale locks. No manual cleanup required.

The table is rendered by renderTable() and uses filteredAgents() to apply the current filter and search. Columns are sortable. Cells are inline-editable — name, requestor, description, and owner fields are <input> elements that call updateField() on change and auto-save.

The Board view (renderKanban()) shows agents as cards grouped into 5 phase columns: Idea, Design, Build, Test, Live. Tabled agents never appear in normal board columns — they have their own dedicated view.

Each card shows: agent name + next handoff chip, requestor, description (truncated to 90 chars), tags, progressive date strip (for agents with dates set), and a footer with priority badge and added date. Clicking any card opens the edit modal.

The Tabled view is a parking lot for agents that are on hold — waiting for a policy decision, vendor access, budget approval, or a dependency that hasn't cleared yet. Tabled agents are invisible everywhere else in the tracker — they do not appear in any phase filter, any board column, or any summary card count.

To table an agent: open the edit modal, check the ⏸ Tabled tag. To un-table: uncheck it and re-save.

The Tabled filter is available in both Table and Board views. In Board view, a single purple-accented column appears with all tabled agents showing their original phase as a badge, so you know where they'll re-enter the pipeline when unblocked.

The modal is 820px wide and designed to fit on a single screen without scrolling. It opens via openModal() (new) or openEditModal(idx) (edit). Saved by clicking Save or pressing Ctrl+Enter. Closed by clicking Cancel, the ✕ button, or pressing Escape.

The Handoff column in the table view is designed for technicians — it answers "when is the next thing landing on my plate?" at a glance. It shows one primary date prominently and any other set dates dimmed below it.

Clicking ⎙ Print opens a pre-print dialog modal that collects report metadata before generating the document. The report renders in a new window as a fully self-contained HTML document, then automatically opens the browser print dialog. The browser's "Save as PDF" option produces a properly named PDF file.

All configuration is at the top of the script block, clearly marked. No build step, no env file — just edit the constants directly in the HTML file.

The tracker uses exactly three SharePoint REST API endpoints — all called from within the browser using the user's existing SharePoint authentication session. No credentials are stored in the file.

The filteredAgents() function is the single source of truth for what appears in every view. Understanding its rules prevents confusion about why agents appear or disappear.

SharePoint persistence requires one config change and one manual step in SharePoint before the first save. Once configured, saves happen automatically with every change — the same as the rest of the platform suite.