You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
- Fix Plan Gate deadlock: stale-plan latch now warns (never hard-blocks) on tool execution, aligned with codex exec-policy philosophy. A mutating tool on a stale plan receives a reminder but always runs.
6
6
- Fix goal-loop scorer false positives: `extractValidationResults` now scopes extraction to declared validation commands only (toolCallId→command mapping), with latest-wins per command. Diagnostic bash calls no longer poison the score.
7
7
- Fix cancel/loop test flake: `maxRetries:0` in the test provider config prevents AI SDK exponential-backoff retries against the intentionally-dead test URL; per-test budgets raised from 3 s to 15 s.
8
-
-Bump desktop app to 1.4.2.
8
+
-Release Desktop 1.4.2 with DeepAgent Core V4.0.4.
9
9
- Publishing truth: fix quick-start command (`deepagent-code run`), comment out unpublished npm install, unify domain to `deepagent.ltd`, replace `lessweb`/`anomalyco` org handles, update SECURITY.md supported-version line and M-CRED status, update CHANGELOG.
@@ -91,17 +91,16 @@ For high-risk decisions, convene an **Expert Panel**. Correctness, security, per
91
91
92
92
Project IM brings people and agents into the same thread. Mention an agent to start a scoped run with project context, stream its progress, inspect its artifacts, and keep the answer attached to the conversation that requested it.
93
93
94
-
## DeepAgent Core V4.1
94
+
## DeepAgent Core V4.0.4
95
95
96
-
V4.1 brings the complete DeepAgent control plane together:
96
+
V4.0.4 closes production contract gaps while keeping the current turn engine stable:
97
97
98
-
-**Durable Session V2:** prompt admission is persisted before execution; exact retries do not duplicate user intent; same-session wakes coalesce safely.
99
-
-**One provider-turn contract:** native and AI SDK providers share the same budget, permission, artifact, audit, learning, and close lifecycle.
100
-
-**Single durable truth:** DocumentStore owns documents, plans, learning candidates, governance state, and version conflicts through atomic, recoverable writes.
-**Consumer-driven goals:**`goal.tick.requested` claims and executes one idempotent tick, records facts, and schedules the next tick only when the durable goal remains eligible.
103
-
-**Human oversight:** approval queues, trace correlation, takeover, rollback, Wiki archives, notifications, and organization/workspace isolation remain part of the execution path.
104
-
-**Secure integrations:** MCP credentials use environment references or native OS secret storage; catalog risk, runtime permissions, trusted sources, and tool capability checks fail closed.
98
+
-**Single durable truth:** DocumentStore uses atomic, recoverable writes for documents, plans, learning candidates, governance state, and version conflicts.
99
+
-**Isolated subagents:** write-capable subagents use dedicated worktrees by default and return their changes to the parent workspace through a bounded, conflict-aware path.
100
+
-**Reliable event delivery:** the Event Bus has a transport seam, durable consumer offsets, offline catch-up, real priority ordering, and observable queue depth.
101
+
-**Governed learning and goals:** knowledge promotion is tied to review evidence and ship-gate snapshots; event-driven goal ticks remain idempotent and respect quiet hours.
102
+
-**Secure integrations:** MCP credentials use environment references or native OS secret storage on macOS, Linux, and Windows; capability and source checks fail closed.
103
+
-**Publishing truth:** installation, CLI examples, release metadata, public domains, and supported-version documentation match the product that is actually shipped.
> **Public design overview.** Internal implementation details and roadmap docs live in the private `docs/` tree (not version-controlled). This directory contains the publicly visible architectural narrative.
3
+
> **Public design overview for DeepAgent Core V4.0.4 / Desktop 1.4.2.** Internal implementation details and roadmap documents live in the private `docs/` tree and are intentionally not version-controlled.
4
4
5
5
---
6
6
7
7
## What is DeepAgent Code?
8
8
9
9
DeepAgent Code is an AI coding agent that adds a **control plane** on top of the [opencode](https://github.com/sst/opencode) runtime. It keeps the proven opencode foundations (runtime, tool, MCP, session, provider stack) and layers in:
10
10
11
-
-**Durable document memory** — knowledge base with retrieval gates, dedup, and merge
12
-
-**Context assembly** — selective, evidence-backed context building (not raw file dumps)
13
-
-**Plan system** — structured task planning with staleness detection and rollback
-**Domain adapters** — pluggable domain packs for specialized workflows
11
+
-**Durable document and project memory** — atomic, recoverable storage with retrieval gates, provenance, governance, and conflict detection
12
+
-**Connected context** — selective, evidence-backed assembly across code, knowledge, project memory, and execution documents
13
+
-**Plans and long-running goals** — structured plans, stale-state detection, validation evidence, bounded retries, and human control
14
+
-**Event-driven coordination** — durable delivery, priority routing, offline catch-up, idempotent goal ticks, and observable queue state
15
+
-**Isolated agent collaboration** — bounded subagents, worktree isolation for write-capable workers, and conflict-aware change return
16
16
-**AI IDE microservice** — LSP-backed semantic code navigation via `code_intel`
17
-
-**MCP catalog** — curated, one-click-enable MCP servers with safety tiers
17
+
-**Secure MCP catalog** — curated integrations, derived safety tiers, environment references, and native OS secret storage
18
18
19
19
---
20
20
21
21
## Architectural Principles
22
22
23
23
### 1. Enhance, don't replace
24
24
25
-
DeepAgent is built **on top of** the opencode agent/runtime/session/tool/MCP stack. It does not rewrite the execution engine, tool system, or provider layer. The default agent behavior is not degraded. The lower-strength `general` mode stays close to the inherited runtime contract.
25
+
DeepAgent is built **on top of** the opencode agent/runtime/session/tool/MCP stack. V4.0.4 strengthens the control plane without replacing the current turn engine, tool system, or provider layer.
26
26
27
-
### 2. Control-plane only
27
+
### 2. One durable authority per concern
28
28
29
-
DeepAgent is responsible for **strategy / context / budget / audit / verification / document graph**. It does not directly spawn LSP processes or execute MCP tools — those go through the existing `LSP.Service` and `MCP.Service` respectively.
29
+
Documents, plans, event delivery state, knowledge promotion, and goal progress each have one authoritative durable store. In-memory state may accelerate delivery, but it cannot become a second source of truth.
30
30
31
31
### 3. Full tool output does not enter context
32
32
@@ -36,6 +36,10 @@ Per the deterministic task control contract: raw LSP results, diagnostic dumps,
36
36
37
37
MCP catalog entries default to **not connected** (zero startup overhead). Dangerous write operations (force-push, DROP, file delete) require explicit approval. Read-only DB connections enforce restricted-mode at the server level.
38
38
39
+
### 5. Keep execution boundaries explicit
40
+
41
+
Write-capable subagents run in isolated worktrees by default. Event consumers claim durable work with idempotency and retry boundaries. Users retain explicit paths to approve, steer, pause, resume, take over, or roll back long-running work.
**Credentials** are declared by key name in the catalog template (`CredentialSpec`). Values are filled at enable-time.
97
-
98
-
> **Known limitation (V3.4):** credential values are stored in plaintext in the local config file. Do not commit config files containing credentials to version control. A secure-storage mechanism (OS keyring, aligned with the codex approach) is planned for V3.5.
99
+
**Credentials** are declared by key name in the catalog template (`CredentialSpec`). Configuration stores environment references or `secret://` handles instead of plaintext values. Handles resolve at connection time through macOS Keychain, Linux Secret Service (`libsecret`), or Windows DPAPI-backed credential storage.
0 commit comments