Skip to content

feat(web): Feeds page, and the publishing nodes on the canvas - #555

Merged
adeelahmad merged 6 commits into
mainfrom
claude/project-thread-rovv80
Oct 18, 2026
Merged

adeelahmad merged 6 commits into
mainfrom
claude/project-thread-rovv80

Conversation

@adeelahmad

@adeelahmad adeelahmad commented Oct 18, 2026 •

Copy link
Copy Markdown
Owner

Description

Before: feeds and the publishing nodes existed only in the API and MCP (#534, and the routine nodes in #547). The web app had no page for a feed, and the canvas didn't know the four nodes.

After: Feeds (a button on the Podcasts page, Jump to, and under Explore in the navigation once there is a feed, so a phone's menu stays as short as it was) lists every feed you can read with its kind, namespace, how many items it holds and whether a reader app has fetched it. New feed asks for a title (focused), the kind and the namespace (the current one, or the first you can edit), and Enter makes it and opens its page. A feed's page copies the address in one click, gets a new address (the old one stops at once), lets editors change what readers show (title, author, description, language, category, items shown, artwork, explicit) with Enter saving, lists the items with where each came from (a routine, a person) and takes one out with Undo instead of a confirm. Deleting a feed is undone too: Undo makes it again with its settings and items, at a new address, and says so. On the canvas, Select assets and Select activities are under Data and Publish to feed and Podcast episode under Keep, each with its settings (since, at most, words, status, namespaces, kinds; the feed picked from a list of your feeds; the episode's angle, length, style and sources), a summary on the node, and the checks that say what to fix (a feed to choose, the limits, a graph that publishes nothing). A graph workflow that ends in Publish to feed or Podcast episode is whole without Apply changes.

This is the last of three pull requests for the ask. docs/feeds.md now says built.

How: components/feeds/ (the list, the New feed dialog, the feed page) on the generated Feeds client; workflow-model.ts adds the four nodes, their defaults, summaries and problems, and GRAPH_KEEPS; node-settings.tsx renders their settings with the feeds and namespaces passed down from the workflow editor, which fetches Feeds.listFeeds only for graph workflows.

Motivation and Context

Adeel's ask in the project: RSS and iTunes podcast endpoints from routines, so a routine can pick part of the graph and publish a podcast or timeline events through a feed. The web app is where someone sets that up and checks on it.

Screenshots (if appropriate):

n/a

Steps to reproduce (if appropriate):

Podcasts → Feeds → New feed (Enter), copy the address into a podcast app; Workflows → new graph workflow → Select assets → Podcast episode, pick the feed, Try.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change; ! in the title)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests (__tests__/feeds-ui.test.tsx, 5 tests; __tests__/workflow-flow.test.ts, 3 tests under "publishing from the graph"; __tests__/nav-groups.test.tsx, Feeds under Explore once there is a feed).
  • My change requires documentation updates, and I have updated docs/ accordingly (docs/feeds.md "In the web app" and status built, docs/processing.md, docs/requirements.md, README).
  • Users need more than the title to understand it, so I wrote it in changelog.d/feeds-page.md.

Done questions (AGENTS.md)

  • Goal: with this, the whole ask is built: feeds, routines that fill them, and the web app to set it up. Merged on green CI (local CI green: backend, frontend, pre-commit, title; re-checked tsc and the feed tests on the latest main).
  • Agents: nothing new here is web-only; every action on the page is an API call an agent already makes (/api/v1/feeds, the MCP feed tools, /api/v1/workflows).
  • Zero setup: no new prerequisite, .env or step.
  • Fewest clicks: New feed fills the kind and namespace and Enter makes it; the address copies in one click; Enter saves settings; Remove and Delete have Undo, no confirm dialog; the nav gains no item until there is a feed, so the phone Clicks journeys take no extra swipe.
  • Configurable: a feed's reader-facing settings are editable on its page, each with a default; no new server setting, nothing in the wizard.
  • Light: a page and components; the feeds list is fetched only for graph workflows, cached a minute; no new dependency.
  • Private and secure: the page shows a feed only to its namespace's readers and the editing to its editors (can("editor")); the address is shown as the API seals it; nothing new leaves the machine.
  • Cost: no model calls.
  • User decides: nothing publishes until someone makes a feed and puts the nodes on a routine; existing pages and defaults are unchanged.
  • Upgrades: no change to stored data.
  • Honest: docs/feeds.md says built, with the checks named in docs/requirements.md; the page says when no app has read a feed yet, and who or what added each item.
  • Tests, docs updated; no generated file changes (no API change).
  • Open standards: builds on the RSS 2.0 and iTunes feeds; MIT kept.
  • Result reported in the thread with the PR; "refine later" items (an XML preview on the feed page, Try listing what Publish to feed would add) are in docs/feeds.md.
  • Reuse: the generated Feeds client, useArchive, Dialog (Enter submits), Panel, Badge, CodeBlock (copy), EmptyState, useToast with an action for Undo, and the workflow editor's existing NodeSettings and summary code.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD

Feeds under Explore lists a namespace's feeds; New feed asks for a title,
kind and namespace and opens the feed's page, which copies the private
address, gets a new one, edits what readers show, and takes items out or
deletes the feed with Undo instead of a confirm. Graph workflows get Select
assets, Select activities, Publish to feed and Podcast episode in the palette,
with the feed picked from a list and the canvas saying what to fix.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD
@adeelahmad adeelahmad self-assigned this Oct 18, 2026
…dcasts

A Feeds item always in the nav pushed Admin below a phone's screen, so two
journeys took one more swipe. Like Approvals, it shows while there is
something to count; the Podcasts page and Jump to lead there before that.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD
Keeps main's entity filter tests beside the feed ones, moves the web app's
Feeds note to Unreleased, and lists #400 (released in v0.15.0) as built
with its checks, which the requirements check asks for.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD
Keeps both the publishing nodes and main's automation actions in the
workflow model, canvas and settings, and main's wording for #400.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD
The changelog paragraph moves to changelog.d/feeds-page.md, as AGENTS.md now asks.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CDEiKGoyQX8Vmnv9bi5JpD
@adeelahmad
adeelahmad merged commit 87bed5b into main Oct 18, 2026
10 of 11 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-rovv80 branch October 18, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants