The situation
An interaction-rich workbench needs Presets, Plans, approvals, Trajectory, Threads, and Files. Rebuilding the Agent loop first delays the parts users can actually see and judge.
All reference builds
Independent reference build
DeepSeek workbench on Awaken Agents
Keep the workbench experience and use Agents to run its tasks.
This independent build keeps Presets, Trajectory, approvals, Skills, subagents, and deliverables in the workbench. The browser and product API remain projections over Awaken Sessions and committed Events.
Best for: Teams building Agent IDEs, coding workbenches, or other interaction-rich Agent products.
Reference build with fixture and live browser evidence
This is an independent reference reimplementation. It does not imply a DeepSeek partnership, sponsorship, or endorsement.
First useful result
Start one Preset-driven Session, review its Plan, approve a tool, and reopen the same Trajectory after an interruption.
Product shape
Build an advanced Agent workbench
Your application keeps
Preset UX, browser preferences, product projections, and a stateless workbench Session API and Interaction MCP.
Awaken provides
Managed Sessions, events, model routing, credentials, tools, permissions, compaction, resources, subagents, Worker, and Sandbox.
What is available today
Check the status before you invest more.
The fixed source includes its shared dependencies. Local checks, desktop and narrow-screen browser workflows, and a fresh real DeepSeek journey on local Kubernetes passed. The video shows the deterministic demo; platform release qualification and customer outcomes are separate.
- Committed application baseline
- 3faa59acc1265695bfba15fc19d4a7786e81c641
Each application has its own code and qualification. The Agents documentation revision is a separate baseline.
Source archive SHA-256: 47ac3434ad229ba7a2abaf12808355edc5f162a5aa977aed2efa12d05f3665a5
Download the fixed source- Fixture-tested
The deterministic Managed API demo exercises the browser, workbench Session API, official SDK, and committed-event projection.
Where to check: e2e/harness.spec.ts
- Audited contract
Native, Equivalent, Presentation, and Unavailable capabilities have explicit boundaries.
Where to check: docs/ui-parity.md
- Live browser gate passed
A fresh local Kubernetes run exercised all four Presets, genuine Skill delivery, permissions, tools, Plan, Creator, questions, delegation and reconnect.
Where to check: e2e/live/harness-live.spec.ts
Use this reference
Start with one clear build and validation path.
- 01Run the deterministic demo before adding provider credentials
- 02Trace one Preset-driven Session from the browser through the product API to committed Events
- 03Replace the fixture with your published Agent without adding browser-owned execution state