Quickstart

August 16, 2026 ยท View on GitHub

This guide gets an existing DeepSeek Harness profile running with Fullstack Expert in about five minutes.

Requirements

  • Node.js supported by your installed DeepSeek Harness release
  • A working dsh command
  • A profile with the normal coding capabilities: filesystem, tools, system prompt, skills, shell, jobs, and approval
  • Access to the tagged GitHub release/local checkout (or the npm package once published)
  • pnpm on PATH for profile dependency installation

Fullstack Expert is an optional workflow layer. It does not replace the Harness shell, filesystem, browser, database, model, or approval providers.

1. Install the plugin into a profile

For the public GitHub release:

dsh plugin --profile web add git+https://github.com/adithya-hmt/fullstack-expert.git#v0.1.1

If npm publication is enabled later, the equivalent package spec is:

dsh plugin --profile web add @deepseek-ai/fullstack-expert

For a local checkout, run this from the directory containing the cloned repository:

dsh plugin --profile web add .

Use your actual profile name instead of web if you run another profile.

2. Confirm the profile layer

Inspect the composed configuration before starting a session:

dsh --profile web --dump-config

You should see a fullstack-expert row. If the row is absent, check that the package is installed into the same profile you are starting and that the package manager completed successfully.

3. Start Harness

dsh --profile web

Ask the agent to work on a real feature, bug, review, or refactor. For substantial work it should use:

  • fullstack_plan to inspect the repository and produce a vertical-slice plan.
  • Native Harness tools to implement and run checks.
  • fullstack_check to record bounded evidence and distinguish pass, fail, and unknown.

A typical request is:

Inspect this repository, plan the smallest safe vertical slice for adding project labels, implement it using existing patterns, run the relevant checks, and do not claim completion without fresh verification evidence.

4. Configure the overlay manually (optional)

If you prefer a user-owned patch instead of dsh plugin add, add the row to your profile's cordis.patch.yml:

- insert:
    - id: fullstack-expert
      name: '@deepseek-ai/fullstack-expert'
      config:
        registerSkills: true
        enablePlanningTool: true
        enableCheckTool: true
        enableShellGuard: true

The profile must already provide the native services named in the project's composition notes. Do not edit the Harness installation's shipped preset; use a profile or copied user preset.

What success looks like

The plugin is working when:

  1. Harness boots without a plugin resolution or schema error.
  2. The agent can call fullstack_plan for a repository request.
  3. The agent can call fullstack_check and returns explicit evidence.
  4. Sensitive operations continue to use native Harness approval.
  5. The agent reports unknown checks honestly instead of converting missing capability into a pass.

Troubleshooting

fullstack_plan says the filesystem is unavailable

Add the native filesystem provider/tool to the profile. Fullstack Expert intentionally fails closed rather than pretending it inspected a project.

The plugin row does not appear

Run dsh plugin --profile web list and dsh --profile web --dump-config. Confirm the package name and profile name, then restart Harness after a successful package operation.

Supabase checks do not connect to a project

That is intentional in V0.1. Supabase support detects local repository evidence only. Login, linking, migrations, pushes, resets, pulls, and deploys remain explicit sensitive operations owned by the surrounding Harness/tool composition.

Browser verification is unknown

V0.1 does not add a browser driver. Compose a native browser capability and collect actual runtime/UI evidence when the task requires browser verification.

Next steps