DeepSeek Harness Client Slots: A Placement Map
A slot is not “find a place to render a component”; it is “declare where this content belongs, how many copies may exist, and what lifecycle it follows.” Those three questions map to position, cardinality, and scope (source). Pick a position and ignore the other two, and you get “it shows, but switching sessions loses it” or “two plugins installed, only one visible.”
DeepSeek Harness: A slot is a position contract
A component answers “what does it look like”; a slot answers “where, how many, and when does it die.” A plugin registers content and metadata; the host renders it. (source)
Two constraints follow:
- The host owns placement — you choose a slot name, not CSS coordinates; the same slot can move with the layout.
- Scope owns lifecycle — content is not eternal; it follows the slot's scope.
Treating a slot as a normal mount produces “a global button inside settings” or “a session-only action in the sidebar.” The first is the wrong position; the second is the wrong lifecycle.
Ask three questions: which region does this belong to, how many entries, and global or session-bound. Answer them before choosing a slot name.
DeepSeek Harness: Four placement families
Client slots fall into four families, each with a different job. A placement map (source):
| Region | Typical slot | Use it for | Avoid |
|---|---|---|---|
| Header | detail actions / badge | Actions and status for the current object | Global navigation, long forms |
| Sidebar | pane-tab, right sidebar | Persistent workbench and resources | One-off notices |
| Settings | settings.section | Configuration and settings cards | High-frequency action buttons |
| Session | message or session slots | Content bound to the current session | Global stats, cross-session tools |
Header and sidebar mix easily. Header is “what can I do to this object”; sidebar is “a tool that is always here.” A persistent tool in the header disappears on navigation; a one-off action in the sidebar occupies space forever.
Settings and session mix too. Settings is “configure once, applies long”; session is “related to this conversation.” A session action in settings survives a switch, so users think it is global.
The four families are semantic, not exact names. Use official docs for slot names, but “object, persistent, config, session” covers most choices.
DeepSeek Harness: Cardinality and scope
After position, cardinality and scope decide stability. They cause duplicates, disappearance, and cross-session leakage. (source)
Cardinality has three questions:
- Can there be more than one? A single-entry slot rejects or overrides a second registration.
- How is it addressed? Id-addressed slots reject a duplicate id.
- Does order matter? List slots need explicit ordering, or render order may vary.
Scope has two:
- Global or session-bound? Session content should rebuild on switch; global content should persist.
- Does closing the panel destroy it? A sidebar panel should unload and clean subscriptions on close.
A rule: if the content holds session state, use session scope; if it only holds global config, use global scope. Do not use global everywhere to “save work,” or sessions leak into each other.
Wrong cardinality and scope usually survive single-plugin testing and break when a second plugin or a session switch arrives.
DeepSeek Harness: Three wrong-slot symptoms
Three symptoms cover most placement mistakes. Use them to trace back to position, count, or scope (source):
- Not visible — wrong slot name, mismatched scope, or the host does not render that slot.
- Duplicated — a list slot with a fixed id, or the same content registered twice.
- Disappears/leaks on session switch — scope is wrong: session content uses global, or global content uses session.
“Not visible” is often misread as “the plugin did not load.” Register the same content in a known slot; if it shows, the slot name or scope is wrong. If it still does not, inspect client module loading.
Duplication usually comes from ids. In an id-addressed slot, two plugins with the same id cause the second to fail or be ignored; the result is “two installed, one visible.”
Session leakage is the subtlest. A global scope keeps the previous session's data; a session scope destroys global content on switch, making a feature look intermittent.
DeepSeek Harness: Three placement examples
Three examples cover common needs. Match the closest (source):
- Settings card — settings region, single entry, global scope; it appears only on the settings page and persists after save.
- Sidebar workbench — pane-tab, single entry, panel scope; closing the panel unloads it and cleans subscriptions.
- Session action — a session-related slot, session scope; it rebuilds on switch and never shows another session's data.
The shared rule is “content lifecycle matches position semantics.” A settings card lives long; a panel follows the panel; a session action follows the session.
For a need outside the examples, use four questions: region, count, lifecycle, cleanup on close. Then find the exact slot name.
DeepSeek Harness: Verify display, duplication, and switching
Do not stop at “it rendered.” Three checks (source):
- Display — the content appears in the target page and position.
- Duplication — register a second similar entry; does it coexist, reject, or override as cardinality says?
- Switch — change sessions, close the panel, and refresh; does the content rebuild or persist per scope?
All three mean the slot is correct. Passing only the first often hides cross-session data; passing the first two often hides a subscription that survives panel close.
The existing dev-client-slots covers one Slot's declaration and props, and dev-sidebar-right covers the right sidebar; this article covers the placement map. Choose position, count, and scope, and client extension stops being trial and error.
FAQ
A DeepSeek Harness client slot is a host-provided position contract that also decides count and scope; a normal component only renders. The slot controls placement and lifecycle.
In DeepSeek Harness, a pane-tab is a sidebar panel tab for a persistent workbench; a settings slot is for configuration. One is for daily operation, the other for setup, and swapping them creates odd behavior.
In DeepSeek Harness, cardinality is how many entries a slot allows and how they are addressed, such as single, list, or by id. Choosing wrong causes overrides, duplicates, or missing content.
In DeepSeek Harness, the slot scope decides whether content is global or session-bound. Session-bound content should use a session scope; a global scope can show stale data after switching.
Related Terms
- client slot
- A client slot is a reserved DeepSeek Harness client extension position; a plugin registers content and the host decides placement, count, and scope.— DeepSeek Harness reference - Client slots
- cardinality
- Cardinality is a DeepSeek Harness slot limit on entry count and addressing, deciding whether same-name content can coexist and how ids locate it.— DeepSeek Harness reference - Client slots
- scope
- Scope is the DeepSeek Harness slot lifecycle boundary: content can live globally or bind to a session, panel, or page.— DeepSeek Harness reference - Client slots
- pane-tab
- A pane-tab is a sidebar panel tab in DeepSeek Harness, used for a persistent workbench or tool panel.— DeepSeek Harness reference - Client slots
Sources
- DeepSeek Harness reference - Client slots· deepseek-harness
- DeepSeek Harness reference - Client modules· deepseek-harness