depth-two.cordis.snapshot.yml 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  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. backgroundMode: continuable
  27. maxDepth: 2
  28. # Re-pin the recorded model: cordis.yml ships deepseek-v4-pro, but this
  29. # scenario's corpus was captured on flash. A config patch replaces the
  30. # whole app config, so the base fields are restated verbatim.
  31. - id: acp-agent
  32. name: '@deepseek-ai/dsh-acp-demo'
  33. config:
  34. provider: deepseek-official
  35. model: deepseek-v4-flash
  36. persistenceRoot: !!js process.env.DSH_SNAPSHOT_SESSIONS_ROOT ?? './.sessions'
  37. persistenceCompression: none
  38. workspaceContext:
  39. maxBytes: 65536
  40. persona: |
  41. 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.
  42. Verify your work by running the code or tests. Keep answers brief and factual.
  43. - insert:
  44. - id: llm-replay
  45. name: '@deepseek-ai/dsh-llm-replay'
  46. config:
  47. providers:
  48. - id: deepseek-official
  49. name: DeepSeek
  50. models:
  51. - id: deepseek-v4-flash
  52. - id: deepseek-v4-pro