depth-two.cordis.snapshot.yml 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. # Keyless counterpart to depth-two.cordis.yml: apply the depth patch and replace
  2. # the live adapter with per-session replay.
  3. - id: base
  4. name: '@cordisjs/plugin-include'
  5. config:
  6. path: ./cordis.yml
  7. patches:
  8. - id: llm-deepseek
  9. name: '@deepseek-ai/dsh-llm-deepseek'
  10. disabled: true
  11. - id: sandbox
  12. name: '@deepseek-ai/dsh-sandbox-local'
  13. config:
  14. runnerCommand:
  15. - bash
  16. - -c
  17. - while [ "$1" != "--" ]; do shift; done; shift; exec "$@"
  18. - passthrough-runner
  19. runnerFailureSignatures:
  20. - 'passthrough-runner: profile rejected'
  21. - id: tool-subagent
  22. name: '@deepseek-ai/dsh-tool-subagent'
  23. config:
  24. provider: spawn
  25. toolName: subagent
  26. maxDepth: 2
  27. # Re-pin the recorded model: cordis.yml ships deepseek-v4-pro, but this
  28. # scenario's corpus was captured on flash. A config patch replaces the
  29. # whole app config, so the base fields are restated verbatim.
  30. - id: acp-agent
  31. name: '@deepseek-ai/dsh-acp-demo'
  32. config:
  33. provider: deepseek
  34. model: deepseek-v4-flash
  35. persistenceRoot: !!js process.env.DSH_SNAPSHOT_SESSIONS_ROOT ?? './.sessions'
  36. persistenceCompression: none
  37. workspaceContext:
  38. maxBytes: 65536
  39. persona: |
  40. You are a coding assistant powered by the {{model}} model. Your working directory is {{cwd}}. Your bash tool runs under a file sandbox — a `[sandbox: file access denied …]` result is policy, not a command bug.
  41. Verify your work by running the code or tests. Keep answers brief and factual.
  42. - insert:
  43. - id: llm-replay
  44. name: '@deepseek-ai/dsh-llm-replay'
  45. config:
  46. providers:
  47. - id: deepseek
  48. name: DeepSeek
  49. models:
  50. - id: deepseek-v4-flash
  51. - id: deepseek-v4-pro