Changelog

The work we’ve shipped, in the open.

This is the FeatureJet team’s public changelog, rendered from the same live board we use to collect and close the loop on feedback.

Open the public board Subscribe with RSS

Latest shipments

One changelog, one source of truth.

RSS

Jul 23, 2026Shipped
Expose queue ranking through the MCP server
Found while running our own roadmap through the agent work queue: the queue is owner-ranked (queue_rank, lower = sooner), but the MCP update_post tool doesn't expose it — ranking currently requires the dashboard or the REST API. If the queue is the surface agents work from, its curation knob belongs on the same surface. Proposal: add queue_rank to the MCP update_post tool (write scope, owner/admin-keyed only, same authorization as the dashboard PATCH).
Jul 23, 2026Shipped
Board templates
Start faster with ready-made board setups for SaaS, mobile apps, and internal tools — statuses, tags, and welcome copy preconfigured.

Team update (2026-07-18): The first slice of this is now planned: example-post seeding for empty boards. A brand-new board gets a handful of clearly-marked example posts so your first visitors never land on a blank page — keep them or delete them as you like. Preconfigured statuses, tags, and welcome copy come after that.
Jul 22, 2026Shipped
Agents propose Shipped; you confirm
An agent that finishes work shouldn't be the one telling your users something shipped. We're adding an implemented-awaiting-review state: an agent proposes it, you confirm with one click, and voters hear about it after a human has confirmed — not before. The human gate stays where honesty needs it.
Jul 20, 2026Shipped
Outbound webhooks
Get a webhook when a post is created, changes status, or gets a comment — pipe board activity into Slack, your data warehouse, or any custom workflow. The foundation for deeper integrations.

Team update (2026-07-18): We picked this up as part of making boards agent-operable. The first version covers two events — post created and status changed — delivered as signed HTTP POSTs, which is enough to trigger an agent run whenever new feedback lands or a status moves. More event types can follow once those two are solid. Now shipped.
Jul 20, 2026Shipped
Write-scoped API keys for agents
An agent that claims work and files comments doesn't need a key that can rewrite your whole board. We added scoped API keys, so you can mint one limited to reading the queue, claiming posts, writing comments, and proposing status changes. If a key ever leaks, the blast radius stays small — revoke it and mint another.
Jul 19, 2026Shipped
One-click unattended runner recipe
Once your board has a queue and claims, the remaining piece is a scheduler. We put together a first-party recipe — a GitHub Action and a cron template — that runs your coding agent against your queue on whatever schedule you choose. FeatureJet stays the queue; your own infrastructure does the running; setup should take a few minutes, not an afternoon.
Jul 19, 2026Shipped
Attach implementation evidence to posts
When an agent (or a person) finishes work on a request, the receipts should live on the post itself. We added structured evidence fields — branch, commit, pull request, and a transcript link — set through the API and MCP and rendered right on the post. Anyone who voted can see exactly what was built, not just a status change.
Jul 19, 2026Shipped
Agent queue: one call for the next item, in your order
Today an agent working your board has to list posts, sort them, and guess what matters most. We added a get_queue call that returns the top unclaimed item in the order you set — your curation decides what's next up, with votes as an input rather than the ruling. One call, one answer: here's the next thing to build.
Jul 19, 2026Shipped
Claim a post while an agent works on it
When you point more than one agent at your board, two of them can pick up the same request and duplicate the work. We added an atomic claim on posts — through the API and MCP — with a lease that expires on its own if the agent goes quiet. Claim, extend, or release; while a claim is live, other agents see the post as taken. That makes unattended runs safe to leave alone.
Jul 19, 2026Shipped
Conversion events on our marketing site (Umami)
We use Umami — cookieless, privacy-friendly analytics — on featurejet.com. We're adding conversion events (signup started, signup completed, trial converted) so we can tell which pages actually help people decide and which ones need rework.

Aggregate counts only, on our own site, no ad trackers. We're posting it here because this board is our own roadmap and we run it in the open.

What we built (Team update, 2026-07-18): Conversion events are live on the marketing site via our self-hosted Umami: click and submit events across the pricing → signup → checkout funnel (signup-click with the chosen billing interval, signup-submit, checkout-click). Why it matters: We can now tell which pages actually help people decide — and rework the ones that don't — from our own cookieless analytics instead of ad trackers. How to use it: Nothing to do on your end; this is instrumentation on our own site. This post was the plan in the open — this update is it shipped.

Clarification (Team, 2026-07-19): alongside aggregate counts we run self-hosted session replay on our marketing site only — to fix confusing pages. Nothing leaves our servers, no third-party trackers, and it never runs on your board or records your voters. Details in our privacy policy.
Jul 19, 2026Shipped
7-day free trial for new accounts
We're adding a 7-day free trial to every new account. You get the full product — public board, roadmap, changelog, widget, API and MCP access — with no feature gates, so you can put a real board in front of real users before paying.

This is in progress now. We'll update this post when it's live.

What we built (Team update, 2026-07-18): Every new account now starts with a 7-day free trial of the full product — public board, roadmap, changelog, widget, API and MCP access, no feature gates. Why it matters: You can put a real board in front of real users and decide with evidence before paying anything. How to use it: Sign up at https://featurejet.com/signup — you add a card at checkout and the 7 days start ($15/month or $119/year after that). Cancel during the trial and your board stays up read-only.
Jul 19, 2026Shipped
Public REST API
Programmatic access to boards, posts, and votes.

Webhooks are tracked separately — see the Outbound webhooks request.

What we built (Team update, 2026-07-18): A public REST API covering boards, posts, votes, comments, changelog, roadmap, and analytics, with official SDKs — featurejet on PyPI for Python and @featurejet/sdk on npm for Node.js. Why it matters: Everything the dashboard does is now scriptable: pull feedback into your own tools, automate triage and status changes, or build reporting on top of your board. How to use it: Create an API key in Dashboard → API keys, then follow https://featurejet.com/docs/api and https://featurejet.com/docs/sdks.
Jul 18, 2026Shipped
Connect your AI assistant (MCP)
One-click setup to manage your board from Claude, Cursor, or any MCP-compatible tool: read requests, post ideas, update statuses, and pull your changelog — authenticated with your API key.

What we built (Team update, 2026-07-18): A hosted MCP server at https://mcp.featurejet.com/mcp. Connect Claude, Cursor, or any MCP-compatible tool and it can read requests, post ideas, update statuses, and pull your changelog — authenticated with your API key. Why it matters: Your assistant already knows what your users are asking for; now it can act on it. This status change was made through the MCP server itself. How to use it: Create an API key in the dashboard, add the server URL to your MCP client with Bearer auth. Setup: https://featurejet.com/docs/mcp.
Jul 10, 2026Shipped
Node.js SDK for the FeatureJet API
An official TypeScript-first @featurejet/sdk package on npm with the same surface as the Python SDK: boards, posts, votes, comments, roadmap, changelog, ship stats, and analytics. Typed responses, API-key auth, Node and edge-runtime support — ideal for Next.js apps embedding boards and for CI automation.

What we built (Team update, 2026-07-18): A Node.js SDK for the FeatureJet REST API, published to npm as @featurejet/sdk, covering boards, posts, votes, comments, changelog, and analytics. Why it matters: The same minutes-not-hours promise as the Python SDK, for JavaScript and TypeScript projects. How to use it: npm install @featurejet/sdk, then follow https://featurejet.com/docs/sdks.
Jul 10, 2026Shipped
Python SDK for the FeatureJet API
An official featurejet package on PyPI wrapping the public developer API (/api/v1): boards, posts, votes, comments, roadmap, changelog, ship stats, and analytics. Typed client, API-key auth, pagination helpers — with parity to the MCP server's tools so scripts and AI agents can automate feedback triage, status updates, and exports.

What we built (Team update, 2026-07-18): A Python SDK for the FeatureJet REST API, published to PyPI as featurejet. It covers boards, posts, votes, comments, changelog, and analytics. Why it matters: Scripting against your board should take minutes, not an afternoon of hand-rolling HTTP calls. How to use it: pip install featurejet, then follow https://featurejet.com/docs/sdks.
Jul 9, 2026Shipped
SignalWish is now FeatureJet
Same product, sharper mission: customer feedback, shipped fast.

We rebranded and moved to featurejet.com. Boards now live at yourboard.featurejet.com, the API at api.featurejet.com, and MCP at mcp.featurejet.com. New API keys mint as fj_live_* (existing keys keep working). Everything else — your boards, votes, comments, and integrations — carried over unchanged.

What we built (Team update, 2026-07-18): SignalWish became FeatureJet. The product now lives at https://featurejet.com, and public boards live on their own subdomains, like this one at https://feedback.featurejet.com. Why it matters: One clear name that says what the product does, and one home for everything around it — docs, SDKs, and boards. How to use it: Nothing to do on your end beyond updating bookmarks; the board you're reading is the renamed product.
Jul 9, 2026Shipped
Manage feedback from your AI tools (MCP server)
Connect Claude, Cursor, and other MCP clients to your boards to read posts, triage, and post status updates without leaving your editor.

What we built (Team update, 2026-07-18): The hosted MCP server (https://mcp.featurejet.com/mcp) lets Claude, Cursor, or any MCP-compatible tool manage your board: list and search posts, create and update them, change statuses, and read comments, votes, changelog, and analytics. Why it matters: Feedback triage can happen wherever you already work — this very update was written to the board through the MCP server. How to use it: Create an API key in your dashboard, add the server URL to your MCP client with Bearer auth, and you're set. Docs: https://featurejet.com/docs/mcp.
Jul 9, 2026Shipped
Let AI agents interact with FeatureJet via an MCP Server
Let AI agents interact with FeatureJet via an MCP Server

Connect FeatureJet to Claude, Cursor, and any other MCP-compatible AI tool through a hosted Model Context Protocol server — so your AI assistant can work with your feedback boards directly, without you copy-pasting or switching tabs.

Once connected, an agent could:
- Read and search your boards, posts, votes, and comments — "what are the top 5 requests this month?"
- Triage on your behalf — update statuses (planned / in progress / shipped), merge duplicates, and tag or hide posts
- Draft and post updates — reply to a request or announce a shipped feature across the board
- Summarize signal — turn hundreds of raw posts into a ranked, deduplicated view of what to build next
The idea: your roadmap already lives in FeatureJet, so the AI you're already using to plan and ship should be able to read from it and write back to it natively. Feedback triage is exactly the kind of repetitive, high-volume work worth handing to an agent — and an MCP server makes FeatureJet a first-class tool it can reach, with your permissions and scopes controlling what it's allowed to touch.

Vote if you'd use this, and comment with the tools you'd want it to work with.

What we built (Team update, 2026-07-18): A hosted MCP server at https://mcp.featurejet.com/mcp (Streamable HTTP, authenticated with your API key). It exposes tools for listing boards, reading and searching posts, creating and updating them, and pulling votes, comments, changelog, and analytics. Why it matters: AI agents can work with your feedback board directly — reading requests and filing findings without copy-paste in between. How to use it: Point any MCP-compatible client at https://mcp.featurejet.com/mcp with your API key as a Bearer token. Setup guide: https://featurejet.com/docs/mcp.
Jul 9, 2026Shipped
Board analytics dashboard
Top requests, vote trends, and engagement over time (built on the shared analytics stack).

What we built (Team update, 2026-07-18): An analytics view for your board — top requests, vote trends, and engagement over time — available in the dashboard, through the API, and via the MCP get_analytics tool. Why it matters: Deciding what to build next goes better with the numbers in front of you. How to use it: Dashboard, then your board's analytics; or GET /api/v1/boards/{slug}/analytics — see https://featurejet.com/docs/api.
Jul 9, 2026Shipped
Reactions & upvotes on comments
Let people react to and upvote comments, not just posts.

What we built (Team update, 2026-07-18): Comments have a reaction bar, so you can upvote or react to a comment instead of replying "+1". Why it matters: The best argument in a thread deserves visible support without adding noise to the discussion. How to use it: Open any post's comments and click a reaction.
Jul 9, 2026Shipped
Embeddable feedback widget
Drop a lightweight widget into your app so users can post and vote in context.

What we built (Team update, 2026-07-18): An embeddable widget: one script tag served from https://featurejet.com/embed/v1.js, plus embed views for the board, roadmap, and changelog that drop into your own site. Why it matters: Feedback arrives where your users already are — inside your product — instead of asking them to travel to a separate site. How to use it: Grab your snippet from the board's Embed page in the dashboard; the walkthrough lives at https://featurejet.com/features/feedback-widget.
Jul 7, 2026Shipped
Dark mode for the public board
A dark theme for boards and the roadmap.

What we built (Team update, 2026-07-18): A Light / Dark / System theme toggle on the public board; System follows the visitor's OS preference, and the choice sticks on their device. Why it matters: Nobody demanded it — but a board people keep open should be comfortable to read at any hour. How to use it: Use the theme toggle at the top of https://feedback.featurejet.com.
Jul 7, 2026Shipped
Custom board favicon & logo
Upload your own favicon and logo so the board matches your brand, right down to the browser tab.

What we built (Team update, 2026-07-18): Boards can carry your own logo and favicon in place of ours. Why it matters: Your feedback board is part of your product, so it should look like it belongs to you. How to use it: Upload a logo from your board's settings in the dashboard.
Jul 7, 2026Shipped
Filter by request status on board dashboard
Let admins filter posts by status (open, planned, in progress, shipped, declined) in the board dashboard / management view.

What we built (Team update, 2026-07-18): A status filter on the dashboard's posts table, so admins can slice their board to just planned, in-progress, shipped, or open requests. Why it matters: Triage is faster when you can look at one lane at a time. How to use it: In your dashboard, open the board and pick a status in the filter above the posts table.
Jul 7, 2026Shipped
Categories & tags for posts
Organize requests into categories (Feature, Bug, Integration) and let users filter by them.

What we built (Team update, 2026-07-18): Admins can tag posts with categories, and the board can be filtered by tag; tags also flow through the API and MCP tools. Why it matters: A board of 68 requests needs slicing — by area, by product surface, by whatever scheme fits your project. How to use it: Click a tag on any post to filter the board by it; admins manage tags from the dashboard or via the API.
Jul 7, 2026Shipped
Attach images and files to posts
Add screenshots, mockups, and logs to feature requests and comments so context isn't lost.

What we built (Team update, 2026-07-18): Verified voters can attach images and files to their own posts, and attachments render on the post page for everyone to see. Why it matters: A screenshot usually explains a bug or a request better than a paragraph of description. How to use it: Verify your email on the board, open a post you created, and add your files from there.
Jul 7, 2026Shipped
Data export (CSV / JSON) & RSS feed
Export your posts and votes, and offer an RSS feed for the board and changelog.

What we built (Team update, 2026-07-18): An admin export of every post on a board as CSV or JSON, plus an RSS feed for the changelog. Why it matters: Your data stays yours — take it into a spreadsheet, a script, or wherever you need it, any time. How to use it: Export from your board in the dashboard (CSV or JSON); subscribe to the changelog at https://feedback.featurejet.com/changelog.rss.
Jul 7, 2026Shipped
Internal notes on posts
Team-only notes and discussion on a post, invisible to voters.

What we built (Team update, 2026-07-18): Admins can keep internal notes on any post. They never appear on the public board or in public API responses. Why it matters: Context like customer names or effort estimates stays with the request without going public. How to use it: Open a post in your dashboard and use the internal notes field.
Jul 7, 2026Shipped
Changelog / release notes
A public 'what's new' feed to announce shipped features and close the loop with the people who requested them.

What we built (Team update, 2026-07-18): A public changelog at https://feedback.featurejet.com/changelog where shipped work becomes a readable release history, with an RSS feed to subscribe to. Why it matters: When something you voted for ships, there's a public record you can check — or have delivered to you. How to use it: Open the Changelog tab on the board, or subscribe at https://feedback.featurejet.com/changelog.rss.
Jul 7, 2026Shipped
Pin & feature posts
Pin announcements or key requests to the top of the board.

What we built (Team update, 2026-07-18): Admins can pin a post so it stays at the top of the board. Why it matters: Some posts deserve the spotlight — an announcement, a request you want more signal on — regardless of vote order. How to use it: Pin from the dashboard, or set pinned via update_post in the API or MCP tools.
Jul 7, 2026Shipped
Vote on behalf of a user
Let admins log feedback that came in via support or sales and attribute the vote to that customer.

What we built (Team update, 2026-07-18): Admins can record a vote on behalf of a user — for example, a request that arrived by email or came up on a call. Why it matters: Demand that shows up outside the board still counts, and this keeps it all in one honest tally. How to use it: From your dashboard's posts view, add a vote for a user on any post.
Jul 7, 2026Shipped
Email voters when a request's status changes
Automatically notify everyone who voted when a post moves to Planned, In Progress, or Shipped.

What we built (Team update, 2026-07-18): When a post moves to planned, in progress, or shipped, verified voters who opted in get an email about it. Why it matters: "The thing you asked for shipped" is the whole point of a feedback board — the loop actually closes. How to use it: Vote on a post with your email verified and opt in to updates; we take it from there.
Jul 7, 2026Shipped
Search & filter on the public board
Find and slice posts by keyword, status, and tag.

What we built (Team update, 2026-07-18): A search box plus status filters (New, Planned, In progress, Shipped) and sorting by top-voted or newest, all on the public board. Why it matters: Voters can check whether an idea already exists before posting a duplicate, and find what they care about fast. How to use it: Use the search field and the filter row at the top of https://feedback.featurejet.com.
Jul 7, 2026Shipped
Markdown support in feature descriptions
Format posts and comments with Markdown — headings, lists, code blocks, and links.

What we built (Team update, 2026-07-18): Post descriptions and the board welcome message render Markdown — bold, links, lists, and code. Why it matters: Structured requests are easier to read and easier to act on than walls of plain text. How to use it: Just write Markdown in a post description; it renders on the board. The bold text in this very update is the feature at work.
Jul 7, 2026Shipped
Custom welcome message at the top of your board
Set a short intro or banner so first-time visitors know how to participate.

What we built (Team update, 2026-07-18): Board admins can set a welcome message that appears at the top of the public board, with Markdown support for formatting. Why it matters: The first thing visitors read is yours: what kind of feedback you want and what happens to it once it's posted. How to use it: Dashboard, then your board's settings. The one on this board reads "We love to ship!" — you're looking at the feature right now.
Jul 7, 2026Shipped
Public roadmap view (Planned / In Progress / Shipped)
A shareable roadmap so your users can see what's coming and what just shipped.

What we built (Team update, 2026-07-18): A public roadmap view that groups requests into Planned, In progress, and Shipped columns, driven directly by post statuses — no separate document to keep in sync. Why it matters: Anyone can see what's coming without asking, and votes tell us whether we've got the order right. How to use it: Open the Roadmap tab on the board, or go straight to https://feedback.featurejet.com/roadmap.

Want the full discussion behind an update? Browse the live FeatureJet changelog or subscribe with the RSS feed above.