Choose a ChatGPT plugin interface around the task the user needs to complete. A founder reviewing product context may need a readable record beside the conversation; a founder correcting a draft may need an editor. Begin with the task and the data contract.
This is a design and architecture guide from the 1PC implementation perspective. The suggested extensions are possibilities, not shipped 1PC features.
Match the surface to the task
The official Plugin Extensions reference lists sidebar apps, conversation panels, file viewers and editors, rich forms, and other integration surfaces. These provide different places to inspect, edit, or supply information during work.
Use a panel when a record needs to remain visible while a user reasons about it. Use an editor when exact changes need review. Use a structured form when the task needs fields whose meaning would otherwise be ambiguous.
A founder profile is a good example of the distinction. Weekly hours, budget period, and skills benefit from labeled fields. A discussion of what those constraints mean still belongs in a conversation. Do not make a form do the strategy work.
Keep the context contract separate from the interface
Define what the system reads, what it writes, whose records it can access, and what counts as an accepted update. Then choose a surface that makes those boundaries understandable.
For a product-context workflow, the read contract might include the founder profile, current product overview, and validation findings. The write contract should identify the destination file and what existing content will be replaced. A pleasant panel cannot fix unclear save behavior.
A proposed context-review interaction
1. Load the selected product and relevant current files.
2. Show the facts and assumptions used for this task.
3. Identify stale or conflicting claims.
4. Prepare a concise update for review.
5. Save through the authorized write operation.
6. Show success only when persistence succeeds.
This is an illustrative interaction, not an implemented extension. It emphasizes the moment the user turns conversation into durable company knowledge.
Why 1PC starts with the context layer
The current 1PC repository implements founder profiles, product files, authenticated MCP tools, and Idea Intake and Validation workflows. The web app lets the founder inspect and edit saved knowledge.
The initial technical question is whether accepted knowledge can survive a fresh conversation and be read for the next task. That question can be tested without adding another interface. It also makes error handling concrete: a failed save must not be described as successful memory.
There are no sidebar apps, extension editors, or event subscriptions in this MVP. A future review surface would need to make current-file replacement and the available revision history explicit.
A builder checklist before adding a surface
- Task: describe the user's next action and why the existing path is awkward.
- Context: show which record is selected and what data the task uses.
- Access: enforce ownership on the server, not only in the interface.
- Writes: make the destination and update behavior clear.
- Failures: distinguish loading, missing data, rejected input, and failed persistence.
- Review: offer a readable way to check consequential changes.
- Compatibility: check the supported client and rollout status before promising access.
Prototype one complete task and observe it with a real user. Measure whether the person reaches the intended outcome and understands what changed. A surface count is not a product metric.
Sources and rollout limits
As reviewed October 2, 2026, OpenAI documents composer mentions as desktop-only, with web extensions for Free and Go coming soon. Use the official extension reference for current availability and implementation details.
For the wider founder interpretation, read the DevDay decision guide. For the underlying product workflow, start with ChatGPT for founders and a useful startup context file.
Understand the context layer first.
See how founder profiles, product knowledge, and explicit save rules fit together in the 1PC MVP.
See how 1PC works ↗