SleekplanSleekplan

Help us build Sleekplan.

What we're building, what's next, and what just shipped.

Changelog entries can now be unpublished — on a schedule or by hand — which archives them, and archived entries can be duplicated to publish a fresh copy. Both actions live in the admin today. The scheduled unpublish date is already available through the API, so an integration ca
Feature0
Description: As a developer embedding your widget, I want a public SDK API to programmatically open the native Subscribe/Login prompt from a custom button or action so that I can offer a dedicated “Subscribe” call-to-action within my widget, matching the demo experience without r
Feature0
Description: Add a per-announcement (or global) setting that lets admins disable the "already seen" tracking currently handled via sleekstorage (with cookie fallback), so a specific pop-up or announcement can be shown to a visitor on every visit/session rather than only once. Pro
Feature0
Currently, announcement popups in the Sleekplan widget only expand to full screen when users click specifically on the title. This creates a poor user experience as the clickable area is too small and not intuitive. Proposed improvement: The entire popup area should be clickable
Improvement0
Expected Behavior Tapping the Attach icon should open the appropriate file picker or attachment options, allowing the user to select and attach a file to their post. Current Behavior Tapping the Attach icon does nothing Steps to Reproduce Navigate to the Create Post screen. Enter
Bug1
Description: Add a private flag to createcomment (and to updatecomment, so a comment can be flipped after the fact) that marks the comment as internal — visible to admins only, not to end users on the board. Today createcomment accepts only feedbackid, comment, parent and pinned.
Improvement0
Description: Add an optional author argument to createfeedback, accepting a userid or an email, so a post can be attributed to the end user it came from instead of to the authenticated MCP identity. Same reasoning applies to create_comment. Problem: Every post created through MCP
Improvement0
Description: Add write tools for voting to the MCP server: create a vote, update a vote (e.g. upvote → downvote), and remove a vote. Each should identify the voter by user_id or email — ideally both are accepted, with email resolved to an existing user (and a clear error when no
Feature0
Description: Assign a feedback post to your own coding agent — Claude Code, Cursor, GitHub Copilot, or one you built yourself — and get an implementation plan back, attached to the post as a document. You connect your own agent account, so the work runs on the agent you already p
Feature0
Expected Behavior: should be able to choose other interval (hours/days) Current Behavior: Cannot choose other interval (hours/days) Possible Solution Steps to Reproduce Create pop up survey Enable follow up internal Try to choose days/hours Context (Environment)
Bug1