feat(agent): add DeepSeek Harness runtime - #248
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
22 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
CORAL supports several coding-agent CLIs but cannot currently run DeepSeek's official Harness. This adds first-class support for the official
dsh --profile headlesssurface while preserving CORAL's runtime, model, gateway, sandbox, and shared-state contracts.Changes
dshruntime withdeepseek,deepseek-harness, anddeepseek_harnessaliases..dshshared state,AGENTS.mdinstructions, subprocess logging, sandbox and OS-user isolation support.DEEPSEEK_BASE_URLandDEEPSEEK_API_KEY.agents.modeland the optional provider override the DSH profile defaults.DeepSeek Harness's current headless profile does not expose a session id or resume argument. CORAL restarts therefore create a fresh DSH session with a continuation prompt; existing configurations need no migration, and the compatibility aliases remain accepted.
Test plan
uv run ruff check .— passeduv run ruff format --check .— passed (137 files already formatted)uv run pytest tests/ -q— 694 passed, 1 skippedcd docs && npm run build— passed; 41 static pages generatedgit diff --check— passedThe first full pytest run exposed stale local editable-install version metadata. Reinstalling the checkout into
.venvcorrected the environment; the subsequent full run passed as reported above.Affected areas
coral/agent/(runtime, manager, heartbeat, warmstart)coral/grader/(daemon, TaskGrader, subprocess grader, loader)coral/hub/(attempts, notes, skills, checkpoint)coral/workspace/(project setup, worktrees, grader env)coral/cli/(commands, helpers)coral/hooks/(post_commit / submit_eval)coral/template/(CORAL.md, bundled skills/agents)coral/gateway/(LiteLLM gateway)coral/web/(dashboard)examples/(new or modified task)docs/(docs site)Checklist
devbranch (notmain).feat:,fix:,docs:,refactor:, ...).uv run pytest tests/ -vpasses locally.uv run ruff check .anduv run ruff format --check .pass.tests/for any behavior change.docs/content/, README, or relevant skill under.claude/skills/) for any user-visible or contract change.examples/<task>/:coral validate <task>succeeds and a smoke run produces at least one finalized score. No hidden answer keys committed underseed/.Authored with assistance from Codex. I read every changed line, ran the tests above locally, and verified the behavior described in the test plan.