Running tasks & tools
Give Vicode real project work and check what it did.
You work with Vicode from the composer. Describe what you want, pick a model, and review what it did.
What the tools do
- read and search project files
- write or edit files behind approval
- run commands behind approval
- search connected Project Knowledge
- use skills for reusable task guidance
- use MCP integrations when configured and approved
Running a task
- Type a specific request in the composer.
- Pick an edit mode: Ask permissions, Accept edits, Auto-run, or Full access. The default asks before file changes and commands.
- Watch the run activity and tool calls, approving actions when prompted.
- Review the result, evidence, and any diagnostics.
See Approvals & trust for what each edit mode allows, and for the isolated worktree option that keeps edits out of the workspace until you accept them.
Keep tasks small and specific
Local models do best with clear, specific requests. Open the right project, connect the right notes, and ask for a concrete outcome.