Changelog

Changelog

Changelogs

A new Content space for release notes, edited like a blog and read on one scrolling page.

Every product needs a place to say what shipped. Control Panel now has one: a changelog is a third kind of Content space, next to blogs and Help Centers. It's a folder of .mdx files in the repository, one per release, with a title, a date and a note.

Editing

In Control Panel a changelog works like a blog. Releases are listed newest first in the sidebar, each opens in the same editor as a post, and the Claude panel next to it can draft the note for you — from the commits since the last release, say. Releases can be drafts until you flip the publish switch.

Add one under Settings → Content → Changelogs. The folder is recorded in .paralect.json, so everyone opening the repository gets the same space.

Reading

Published on Relay, a changelog is one long page: the date sits in a column on the left, the release on the right, and older releases load as you scroll. Each release still has its own address at <site>/changelog/<slug>, with a title, description and share card like any article, so a release can be linked from a tweet or a customer email.

This changelog is the first one. It lives at content/changelog in the Control Panel repository.

Relay collections, published assets and your own domain

Help centers get nested collections with their own pages, files from a chat can be shared at a public link, and every site can run on your domain.

Relay, the hosted home of a project's content, learned a lot this week.

Collections with their own pages

A help center's collections can now nest, and each has a page of its own: an icon, a name, a description, an introduction, and then everything inside it. Readers get an "All collections" crumb to walk back up. Collections are edited from the nav in Relay and come from the folder layout when the help center is synced from files (_100_getting-started/index.mdx is the collection's own page).

Drafts on published articles

Editing a published article in Relay no longer changes what readers see straight away. Changes are held in a draft until Publish changes; Discard changes drops them. Control Panel keeps seeing the published version meanwhile.

Published assets

A file Claude produced in a task — an image, a video, an HTML page, a PDF or a Markdown document — opens in a viewer from its preview in the chat, with Open file, Show in Finder and Publish. Publishing puts it at content.paralect.app/<slug>: documents are rendered like a Relay article, anything else is served from the CDN. Assets in project settings lists everything published, with its link and an Unpublish button.

Your own domain

A Relay project's sites live at <slug>.paralect.app/<path> by default. Set a domain in the project's settings and point a CNAME at Vercel, and help.example.com serves the same pages. Custom CSS and <head> scripts apply on the project's own host only; on Relay's host the pages render with them stripped.

Relay, the Build tab and a team page

Help centers and blogs can be published from Control Panel to a hosted site, the dev server has a tab of its own, and the landing page shows how a team works together.

Relay

Relay replaces Ferndesk as the hosted home of a project's content. A help center or a blog kept as .mdx files in the repository is published to a Relay workspace with one click from the space's nav, and from then on the two stay the same while the space is open: files changed on disk (by you, an agent or a pull) go to Relay, what's published in Relay is written back to the files, and a page deleted on either side goes on the other.

Readers get a Ferndesk-style site: a nav of sections and articles, an "On this page" outline, search on ⌘K, light and dark themes. Only published articles are shown. The ids of the linked workspaces are written to .paralect.json, so whoever opens the repository next connects to the same site.

Relay runs at relay.paralect.com on the same accounts as Control Panel: sign in with your Control Panel email.

Build

The dev server moved out of the Run menu and into a Build tab of its own. Start and stop the project's dev script there, watch its output, and pin the pages you're working on as preview tabs.

Help Center covers and auto-linking

Help pages can carry a cover image, the Relay button in the nav shows the sync status, and a docs folder found in the project is linked as a Help Center on its own.

Team

The landing page has a team section with a demo of how a few people and their agents share one board.

Project skills, image styles and file previews

Skills kept in the repository lead the list, article images can follow a house style, and files Claude makes show up under the message that mentions them.

Project skills

Skills in a project's .claude/skills and .agents/skills folders are scoped to that repository: they show first in the Skills tab, and they're edited from within the project like any other file. Skills from your home folder still appear when searched, or when nothing is pinned.

Image styles

The article-image skill now draws in one of the house styles kept in its styles/ folder, and article-image-style writes a new style from reference images and a description. Pick a style when you ask for an image, share the examples with the team, and contribute a style back with a pull request.

File previews

When Claude's reply mentions an image, a video, an HTML page or a PDF it produced, a preview appears below the message. Images referenced in a task's summary render inline, and documents open in their Content editor.

One-file commits

Publish one page while leaving the rest of the working tree alone: the commit dialog lets you pick the files, drafts a message from the diff with Claude, and pushes.

Review and commit, together

The review dialog and the commit dialog were merged into one, with file selection. Chats with Claude about a help page or an article — doc threads — now live next to the document, and MDX pages can hold a skill block that generates content with a skill in place.

The desktop app, Content spaces and device keys

Control Panel ships as a macOS app, blogs and help centers become Content spaces with SEO and publish controls, and each computer gets a key of its own.

A macOS app

The web app and the runner are bundled into one Electron app with auto-updates. Open it, sign in, and the runner starts in the background: no terminal needed. Every request to the local server needs a secret cookie only the app's window has, so other programs and OS users can't call it.

Content spaces

Blogs, Help Centers and Directories are now Content spaces. A project can have any number of each — a help center per role, an internal and an external blog — set under Settings → Content. Pages get SEO fields, a publish switch, and a Notion-style editor with callouts, galleries, pricing tables, cards and embeds. Images upload to Bunny CDN when it's connected.

Pages can also say how they read where they're listed — a shorter title for navigation, a different description for a directory card — under dirSettings, separate from the page's own title and description.

Screenshot notes

Tell Claude how to get into the running app — sign-in steps, test credentials, dialogs to dismiss — once, in project settings. It reads them before taking screenshots and can drive the page with a use_page tool before capturing.

Device keys

Nobody can see or change anyone else's data. Every Convex function checks who is calling. The web server and runner on your computer have no browser session, so after you sign in the page creates a random key for the computer: Convex stores only its SHA-256, and the key goes to ~/.control-panel/devices.json. Signing out revokes it.

Help Center, Blog and Pulse

Long-form content gets a home of its own, and the daily updates feed can sync to Pulse.

Help Center

A Help Center is a tree of MDX pages in the project, edited in Control Panel with a Notion-style editor and synced with Ferndesk or a docs folder. Pages are ordered by their file names (_100_getting-started.mdx), and folders hold a page's children.

Blog

Long-form articles moved out of the feed and into a Blog of their own: a folder of .mdx posts, each with a title, a date, a description and a cover. Claude can draft an article with you — the intro, then the outline, then the closing — writing each piece onto the page as you settle it.

Pulse

The Updates feed can be synced to a Pulse project, so a team's daily notes land where the rest of the company reads them. Articles were removed from the feed, which is now for short daily updates only.

Settings

Project settings were redesigned as a multi-page dialog: general, Claude, content, integrations.

Control Panel 0.1

A local harness for Claude Code — tasks on a checklist, comments that reach the live session, and a feed of what got done.

Control Panel is a local web app that hands tasks to coding agents. Add project folders, write tasks as a Notion-style checklist, and tick a box to hand a task to Claude Code running on your machine. Claude reports back in comments, and every comment you leave is delivered to the live session as a follow-up.

Tasks

↑/↓ move between tasks, Enter adds one below, ⌘↑/⌘↓ reorder, ⌘Enter runs, ⌘O opens, Backspace on an empty row deletes it, and C adds a task from anywhere on the page. A running task streams its current step into the row; when Claude finishes, its summary is posted as a comment and the task moves to Review. Long runs post a progress update every 5 minutes.

Comments and attachments

A comment on a running task is sent into the live session; a comment on a finished task resumes the same session. Comments take file attachments, and the runner hands them to Claude with the follow-up.

Chats

Free-form conversations with Claude in the project folder: a list of chats on the left and a large prompt in the middle. A green dot marks a reply you haven't opened yet.

Commits

A feed of recent commits across branches, grouped by day, with a daily activity chart and streaks. Commit drafts a message with Claude from the diff, and Push pushes the branch. A diff viewer reviews the changes first.

Preview, Skills and the palette

Preview embeds the running app in tabs you can pin. The Skills tab lists .claude/skills and .agents/skills, runs a skill from a chat-style prompt, and edits one with a Markdown editor next to an AI assistant. ⌘K searches skills and projects from anywhere.

Updates

A feed of short daily posts, with a composer, drafts and changelog suggestions drawn from the day's commits.

That's every release.