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. |
||
|---|---|---|
| .. | ||
| prompt_templates | ||
| agent_type_presets.yaml | ||
| builtin_agents.yaml | ||
| builtin_models.yaml.example | ||
| config.yaml | ||