Understand the current directory scope
A UI Extension is an interface or interaction enhancement around DeepSeek Harness. The public directory currently contains 27 curated projects, each with a local preview, a pinned upstream source, and a detail page that explains the relevant setup and compatibility context.
Browse by the capability you need
| Token | Role | Check |
|---|---|---|
| Authoring and layout | Editors, studios, workspace layouts, and content composition aids. | Inspect file writes, generated output, persistence, and keyboard access. |
| Access and navigation | Accessibility, navigation, mobile, localization, and command-discovery improvements. | Test focus, names, shortcuts, locale behavior, reduced motion, and small screens. |
| Feedback and visualization | Rendering, diagrams, previews, motion, and visual state feedback. | Check performance, fallback behavior, motion preferences, and data exposure. |
| Management UI | Controls for models, settings, plugins, sessions, MCP, and workspace state. | Review every privileged action, confirmation, persistence, and rollback path. |
Select and recommend with evidence
- 01
Define the interface problem
Describe the user, task, current failure, environment, and measurable improvement before choosing a record.
- 02
Filter by capability and lane
Use search, capability filters, and distribution status to reduce the set without treating a category as proof.
- 03
Read the complete detail record
Check the immutable source revision, license, asset and trademark disclosures, network behavior, risk disclosure, compatibility state, and rollback note.
- 04
Review the pinned source
Inspect executable code, dependencies, update history, permissions, persistence, and external requests at the exact admitted revision.
- 05
Confirm the fit and open the setup path
Compare the project requirements with your Harness version and workflow, then continue to the pinned source or documented project setup path.
Follow the project setup path
- Open details: compare the preview, workflow tags, compatibility context, and project notes.
- Open the pinned source: read the upstream setup instructions at the exact directory revision.
- Use the project path: follow the upstream release or setup flow that matches your Harness environment.
Evaluate in a controlled workspace
- Use a disposable profile and an isolated environment without production credentials.
- Pin the exact source and dependency graph; record checksums before execution.
- Observe filesystem, process, network, storage, and browser-console behavior.
- Test light, dark, keyboard, reduced-motion, localization, restart, uninstall, and state restoration.
- Publish evidence only after the review policy explicitly admits the result.
Continue exploring
Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
What does this guide verify?
This guide covers: Current 27-record published UI Extensions directory; Capability and collection taxonomy; Preview, pinned-source, and project setup paths
What should I do first?
Start with one of four interface workflows, compare the visual previews, then open a project detail to inspect its pinned source and setup path. The directory keeps discovery, source context, and project guidance together so you can choose by the outcome you need.
Which boundary matters most?
Use the preview to judge visual fit, then open the pinned project source for its setup instructions, requirements, and latest maintenance context. The detail page keeps those handoffs close to the project instead of replacing them with generic warnings.
Continue learning
Continue from the verified evidence
Compare published artifacts or return to the installation documentation.