Reported issues for openpost
Pod holds 11 of 11 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to openpost.
Most discussed
feat: openpost custom backend
Olá Rodrigo
Summary
is it possible to have custom adapters, for instance to post in internal platforms? For instance something driven by Playwright or a custom API?
Problem / Motivation
Having custom adapters would allow to post in internal platforms
What are you trying to do?
posting to internal platforms
Why is this important?
It's a use case that would be great to have solved
Proposed Solution
An adapter interface and maybe having custom adapters that can be integra
Read the thread · 2026-08-05 · closed · external user · 3 comments
Quick Cut: ignore unused sources during export preflight
Problem
Quick Cut validates stream selections for every imported source before export. An unused or disconnected source can block valid enabled segments from another source, even though it contributes no output.
Expected
- Preflight validates only sources referenced by enabled segments.
- Referenced sources with invalid or empty stream selections still fail clearly.
- Merge compatibility and output estimates use the enabled output plan.
Verification
- A focused preflight regression
Read the thread · 2026-08-28 · closed · 2 comments
Architecture program: deepen core seams and retire Post
Problem Statement
OpenPost currently asks users and integrators to trust several competing implementations of the same product rules. Workspace access means active membership in some application paths but also includes credential Workspace scope and Organization identity policy in transport middleware. Publication lifecycle behavior is shared through a transport-shaped handler seam, while the single composer still persists part of its work through the older Post model. Engagement and Messagi
Read the thread · 2026-08-15 · closed · 2 comments
Add instance-admin AI post prompt editor
Summary
Let instance administrators edit the writing instructions used by AI social-post generation without restarting OpenPost.
Acceptance criteria
- List the built-in base prompt and per-platform prompts for X, LinkedIn, Threads, Facebook, Instagram, YouTube, TikTok, Mastodon, and Bluesky.
- Let an unscoped instance administrator using a browser session save or restore each prompt.
- Encrypt overrides at rest and apply them to the next generation request.
- Keep built-in defaults sour
Read the thread · 2026-08-28 · closed · 1 comment
Post compatibility: translate contracts and start the sunset
Parent
#98
What to build
Turn retained Post HTTP routes, old links, CLI compatibility, and Post-backed MCP tools into shallow adapters over Publications, then publish and measure their deprecation. Compatibility must preserve older clients without preserving a second authoring model.
Expected change surfaces
- Post HTTP and MCP compatibility adapters
- Legacy identifier resolution and response projection
- OpenAPI deprecation and compatibility registry
- CLI/MCP help, migration gui
Read the thread · 2026-08-15 · closed · 1 comment
Publication: move planner, CLI, and MCP workflows to canonical contracts
Parent
#98
What to build
Move every maintained non-composer first-party workflow from Post-backed operations to canonical Publication contracts. Users keep familiar product and CLI wording where useful, while identifiers, lifecycle behavior, and output use Publications and Renditions.
Expected change surfaces
- Bounded Publication calendar query and HTTP contract
- Planner and sidebar calendar interfaces
- CLI commands, API client, output, and generated help
- MCP Publication catal
Read the thread · 2026-08-15 · closed · 1 comment
Workspace access: unify the decision and migrate current callers
Parent
#98
What to build
Make Workspace access one transport-independent authorization decision and migrate the current application paths that are not being replaced by later tickets. Equivalent actions must enforce credential Workspace binding, Organization identity policy, active membership, and the required read, edit, or administer level regardless of transport.
Expected change surfaces
- Workspace access and authentication application modules
- HTTP, MCP, and CLI authenticatio
Read the thread · 2026-08-15 · closed · 1 comment
Publish the documentation Markdown surface
Parent
Part of #81.
What to build
Extend the documentation projection from the homepage to every ordinary public documentation source. Authors should keep writing canonical Markdown while the build emits stable .md URLs, a structured documentation llms.txt, discovery metadata in canonical HTML, and a richer checked-in catalogue that acts as the cross-surface contract.
Acceptance criteria
- Every ordinary eligible documentation source produces exactly one canonical HTML page
Read the thread · 2026-08-13 · closed · 1 comment
Most recent
Make every browser-tool page meaningful without JavaScript
Parent
Part of #81.
What to build
Make each public browser-tool page retain its useful meaning before JavaScript runs and in its generated Markdown. The canonical page should explain what the tool does, its inputs and outputs, important limits, privacy or local-processing behavior, and the related OpenPost workflow where one exists. Interactive behavior remains browser-only and is never presented as a public machine API.
Acceptance criteria
- Every browser-tool route explains i
Read the thread · 2026-08-13 · closed · 1 comment
Publish the first Agent-readable public tracer
Parent
Part of #81.
What to build
Make one complete Agent-readable path work on both public content hosts. The marketing and documentation homepages should each produce deterministic /index.md output during their owning production build, publish a minimal useful llms.txt, and advertise the alternate representation from canonical HTML. This ticket establishes the shared generator contract that later tickets extend, while keeping generated artifacts out of Git and leaving the applicat
Read the thread · 2026-08-13 · closed · 1 comment
bug: The OpenPost web UI fail, an closing parenthesis: CREATED_AT) DESC.
Description
The OpenPost web UI fails to load the posts list/dashboard and keeps loading indefinitely or showing a blank list. The backend server returns a 200 status but logs a syntax/validation error regarding an unsupported sort direction string containing an incorrect closing parenthesis: CREATED_AT) DESC.
Steps to Reproduce
- Deploy OpenPost via the official Docker image (
latest). - Generate a domain and access the web UI.
- Log in to the dashboard / posts page.
- Open brow
Read the thread · 2026-05-23 · closed · external user · 1 comment
The remaining reports are on the project's issue tracker.