ChatGPTClaudeGrok / X / CursorGemini

DeepSeek Harness UI vs Session Log: Projection Lag Explained

TroubleshootingPublished 2026-11-18Author: DeepSeek Plugin Market
DeepSeek HarnessDSH pluginsession projectionsession logconsistency
The DeepSeek Harness UI shows a projection, not the log. Learn three mismatch types, why the committed event wins, and when refresh is enough versus a repair.

The UI shows a projection, not the log itself. The DeepSeek Harness session log is the appended event record; a projection folds events into a client view and can be recomputed (source). Two windows showing different content is not automatically data corruption; they may be at different projection points.

DeepSeek Harness: Log is fact, projection is view

The log only appends; the projection can be recomputed. The log records what happened; the projection decides what is displayed now. (source)

Two consequences:

  1. Projection lag is not log loss — the event may be committed while the view has not folded it.
  2. Recomputing a projection is not data repair — it rebuilds the view from the log without changing the log.

Ask whether the event exists in the log before asking which window is right. Event exists, projection missing: display. Event missing, projection shows it: data.

Multiple consumers may project differently: Web, CLI, and SDK each fold. Their views can differ briefly, but the underlying events should agree.

DeepSeek Harness: Three mismatch types

Three sources need three responses. Compare (source):

TypeSymptomFirst action
Projection lagA new message appears laterWait or refresh the projection
Replay differenceOrder or content changes after refreshCheck replay progress and event sequence
Client cacheTwo windows show different contentReopen the window or clear cache

Projection lag is most common. The event is committed, the projection has not folded it; it usually resolves in seconds.

Replay differences look like “the view recomputed under new rules.” A projection upgrade can fold the same events differently; the log is still authoritative.

Client cache is the easiest to misread as corruption. One window holds an old cache, another refreshed; reopening usually aligns them.

DeepSeek Harness: The committed event wins

Check log, sequence, projection, client, in that order. From source to view, not the reverse. (source)

  1. Log — does the event exist?
  2. Sequence — is seq continuous, duplicated, or regressed?
  3. Projection — does the fold include the latest event?
  4. Client — is it using an old cache or subscription?

Log present, sequence normal, projection missing: projection. Log missing: write or persistence. Log and projection present, client missing: cache or subscription.

“It was fixed after refresh” is not proof the problem is gone. A refresh rebuilds the projection or cache and can hide projection lag.

DeepSeek Harness: Refresh vs replay

Refresh is a light rebuild; replay is a full rebuild. Different uses (source):

  • Refresh — re-pull the projection; good for cache or a dropped subscription.
  • Replay — rebuild from the log; good for projection logic changes or a damaged view.
  • Reopen session — re-establish the subscription; good for one session.

Refresh does not change the log or recompute history. Replay folds events again, costs more, and fixes projection-level corruption.

If refresh still mismatches, consider replay. Confirm the log first; replaying missing events produces a “normal” view with holes.

Replay is not a universal repair. A damaged log replays into the same damage; that is when data repair is needed.

DeepSeek Harness: When to repair data

Only three cases justify touching session data. Otherwise refresh or replay (source):

  1. Damaged log — truncated JSONL, sequence gap, parse failure.
  2. Missing events — a key event was never written, so no projection can rebuild it.
  3. Unrebuildable projection — the event format is incompatible and has no migration.

All three are log-layer problems. A complete log with a stale view needs a refresh, not repair.

Back up before repair. The session file is the source of truth; a wrong edit is hard to recover, and backup is cheaper.

Prefer “add the missing event” over “edit the view.” Views can be recomputed, events are long-lived facts. Editing the view only makes the screen look right.

DeepSeek Harness: Verify consistency

Use four steps, not one window. Four checks (source):

  1. Log — the event exists and seq is continuous.
  2. Projection — a replay covers the latest event.
  3. Client — two refreshed windows agree.
  4. Reproduction — record the action that triggered the mismatch; confirm it is not subscription timing.

All four mean log, projection, and client agree. Passing only the first often means projection lag; passing the first two often means cache.

The existing develop-session-projection-units covers projection units, develop-session-log covers log extension, and fix-session-projections-inactive-context covers a specific error; this article covers the three mismatch types. Check the log before the view.

The log is the shared fact; a projection is only one reading of it.

Confirm the fact, then repair the view.

ChatGPTClaudeGrok / X / CursorGemini

FAQ

What is the relationship between the DeepSeek Harness session log and the UI projection?

The DeepSeek Harness session log is the appended fact record; the projection folds committed events into a client view. The log is the source, the projection is a view that can be recomputed.

Did a refresh lose messages because the DeepSeek Harness log changed?

DeepSeek Harness usually does not work that way. A refresh re-reads the DeepSeek Harness projection, which may lag or recompute. Check whether the events still exist before treating it as data loss.

Two DeepSeek Harness windows show the same session differently. Which is correct?

In DeepSeek Harness, the committed events are authoritative. DeepSeek Harness projections can differ temporarily because of client cache, subscription timing, or replay progress.

When should I repair DeepSeek Harness session data?

In DeepSeek Harness, only when the log itself is damaged, events are missing, or a projection cannot be rebuilt. A display lag or cache mismatch calls for refresh or replay, not data repair.

Related Terms

session log
The session log is the append-only DeepSeek Harness event record; it is the common source for model history and client views.— DeepSeek Harness reference - Session
projection
A projection is the DeepSeek Harness process that folds committed events into a client view; it can be recomputed without changing events.— DeepSeek Harness reference - Session projection
replay
Replay rebuilds a view or state from the DeepSeek Harness session log, used for recovery, migration, and projection debugging.— DeepSeek Harness reference - Session projection
client cache
A client cache is local browser or client view data kept to reduce requests; it can be briefly inconsistent with the latest DeepSeek Harness projection.— DeepSeek Harness reference - Session projection

Sources