WeKnora/config
wizardchen 439443e1e1 feat(agent): tell session agents which workspace they are working in
The installer agent was recently given its working directory up front and
stopped prefixing `cd <skill-dir> &&` onto every command. Session agents
never got the same treatment: shell_exec only mentioned /workspace as the
work_dir default, so the model could not tell it was already there, and
execute_skill_script never said scripts run with /workspace as their cwd —
a relative path inside a skill script silently resolves outside the skill.

Describe the workspace once, where each tool is described: shell_exec gains
a Working Directory section (already in /workspace, relative paths, no `cd`
prefix, and each call starts there again so a `cd` does not carry over),
execute_skill_script states its cwd and points at $WEKNORA_SKILL_DIR, and
the skills prompt gains a Workspace section covering input, output and the
per-session package overlay.

Also drop the installer prompt's paragraph about write_sandbox_file and
friends: those tools are not registered in install mode, so the model never
sees them in its schema and the note only spent tokens describing — and
misdescribing — a scope it could not reach.
2026-09-02 16:16:52 +08:00
..
prompt_templates feat(agent): tell session agents which workspace they are working in 2026-09-02 16:16:52 +08:00
agent_type_presets.yaml refactor(agent): remove final_answer tool references and update related logic 2026-06-04 15:48:04 +08:00
builtin_agents.yaml refactor(skills): introduce write_skill_file and edit_skill_file tools for skill directory management 2026-09-02 15:08:05 +08:00
builtin_models.yaml.example feat(builtin-models): add YAML-based declarative config with ${ENV} interpolation 2026-05-26 11:31:01 +08:00
config.yaml 验证完毕 2026-05-15 20:47:01 +08:00