DeepSeek Harness First Test: Setup Errors and Demo Limits
Quick answer: Treat DeepSeek Harness as a preview agent interface, not another name for the model. The recording hits provider errors, then a working OpenRouter route, and ends on a buggy HTML demo. Preview plugins and APIs continue to change.
DeepSeek Harness is an interface for agent work, not simply another name for the DeepSeek model. The AAS recording builds and opens a preview version, changes providers after two different errors and generates a two-stroke-engine HTML demo. The final animation remains buggy.
The current official page describes a plugin-based architecture, desktop/web surfaces and execution-trajectory tools. It also says preview core plugins and APIs continue to change. That is product documentation, not evidence that the historical installation commands still apply unchanged.
Prepare for a preview rather than a finished product
The recording uses Node-related tooling, installs dependencies, builds from source and launches a local web interface. Mike accepts a notice that the harness remains in testing for developers.
The transcript contains fragments such as pnpm install/build and a web-launch command, but it is not a reliable complete command transcript. Use the official project’s current setup instructions. Keep the experiment in a directory you can restore rather than starting in a sensitive production checkout.
Understand what a workspace and plugin selection permit
Mike chooses a project and stays with the standard coding-agent mode. He inspects session and global plugins and notes an alternative creator mode for customization.
A configurable plugin does not automatically need to be enabled. Start with the minimum capabilities required for the test. A shell or file-editing tool can affect the selected workspace, so decide the allowed changes before sending a broad audit request.
Diagnose provider errors separately
The first test against DeepSeek fails with insufficient balance. Mike then tries another provider and gets a model-unavailable error. These are different failures and should not be collapsed into “the harness is broken.”
He next configures OpenRouter and receives a test response. This establishes a working route in that recorded session. It does not establish that the earlier provider configurations were repaired.
Never put a key in a shared transcript or article example. Record provider name, requested model and sanitized error text instead.
Generate a small artifact and inspect the trajectory
After the test, Mike supplies a detailed prompt for a two-stroke-cylinder engine visualization. The harness generates a single HTML file. He inspects the execution trajectory and checks activity in the provider dashboard.
Those views help explain what the agent attempted. They are not a substitute for opening the artifact. A completed file can still contain an unusable animation.
Keep the failed output in the result
Mike opens the HTML in more than one browser. Playback is buggy, and pausing changes its behavior. He asks for fixes, but the animation remains faulty at the end of the spoken source.
A responsible follow-up would preserve a small reproduction, expected behavior and the actual browser error or interaction. The recording does not establish a successful repair, mechanical correctness or a production-ready simulator. Its observed token charges also do not prove the harness is cheaper than another tool on the same task.
Watch the walkthrough
FAQ
Was the final demo working correctly?
No. The spoken source explicitly reports continuing bugs.
Did changing providers fix DeepSeek account access?
No. A different working route is not a repair to the original balance problem.
What should be compared next?
Correct output and recovery behavior on a small fixed task, using the AAS model-testing guide.
You may also like
Build the next one with AI Income Lab
Step-by-step courses, reusable templates, and a community that answers when you get stuck.
Members get the Claude Code & Skills and Codex Tutorials & Courses lessons.
- Courses for builds like this one
- Copy-ready templates
- Ask questions while you build
- Weekly coaching on VIP
