Files, tools, worktrees and scheduled tasks
Understand Fulcrum Code file edits, shell tools, code search, LSP, notebooks, task tracking, isolated Git worktrees and scheduled work.
Read and change a repository
| Tools | What they do | Useful request |
|---|---|---|
| Read, Glob, Grep, Ls | Read files and find paths or matching text | “Find where booking confirmation is handled.” |
| Write, Edit | Create a file or replace matching text | “Change the validation and show the diff.” |
| Bash, Monitor | Run a shell process and follow its output | “Run the focused tests and explain any failure.” |
| LSP | Definitions, references, hover and symbols | “Find callers before changing this function.” |
| REPL, NotebookEdit | Use a Python workspace or edit notebook cells | “Inspect the sample dataset without changing the original.” |
| WebFetch, WebSearch | Read public web material and find references | “Check the official documentation for this API.” |
| ToolSearch | Discover relevant tools when needed | “Find the connected tool for this task.” |
These are agent capabilities, not commands you need to memorise. Describe the task and read the resulting tool activity. Files and web pages can contain misleading instructions; give the agent clear boundaries for how external content should be used.
Keep track of longer work
TodoWrite maintains a session checklist. TaskCreate, TaskGet, TaskList, TaskUpdate and TaskStop support tracked work. Ask for a checklist with verifiable milestones, such as reproduce, fix, test and review. A task marked complete is useful only when the corresponding evidence exists.
Use an isolated Git worktree
Ask the agent to use EnterWorktree for work that should live on a separate branch and working directory. Review the branch and folder it creates before making changes. When finished, inspect the diff, commit or preserve the work, and use ExitWorktree to leave or remove the worktree as appropriate. Do not remove a worktree that contains uncommitted work you still need.
Schedule a bounded task
CronCreate, CronList and CronDelete let the agent create, inspect and remove scheduled work, including five-field cron schedules and one-off @once tasks. Specify what to do, the time zone, the stop condition and the permitted actions. Ask the agent to list the saved schedule to verify it. Confirm the required runtime remains available; creating a schedule alone does not prove an unattended future run will succeed.
When a tool fails
Read the actual error and whether the tool changed anything before failing. Missing executables, permissions and unavailable servers need different fixes. Ask for the smallest diagnostic check that separates those causes. Avoid rerunning a command that may already have sent or published something until its result is reconciled.
Last updated