Filesystem
Sistem Berkas
A tree of files and directories the agent reads from, writes to, and executes within.
The filesystem is the tree of files and directories an agent reads from, writes to, and runs things in. For a coding agent it is the default environment, and it is usually the thing the agent is worst at respecting.
Trees are deceptive. A path looks local and scoped but a glob can match ten thousand files, a symlink can point outside the project, and a path that seems safe can traverse upward. An agent that writes by pattern-matching on names will eventually overwrite something it was never shown.
The other property that bites is size. A directory listing can be enormous, a generated file can be megabytes, and a repository can contain history that dwarfs the working tree. Loading any of it wholesale fills the context with material that will never be relevant.
So the practical rules are: read before writing, match paths exactly rather than by pattern, and let the tooling summarise large directories instead of listing them. Most agent bugs that damage real work are path bugs, and they are all cheap to prevent.
Related terms
Environment
The world the agent acts on: anything outside the harness that it perceives via tool results and changes via tool calls.
Tool
A function the model is allowed to call, like reading a file or running a command.
Sandbox
An isolated environment the agent runs inside: container, VM, or restricted shell. It limits the blast radius.
Context Engineering
Deciding what goes into the model's context, and what stays out.
Progressive Disclosure
Show the model only the detail it needs right now, and load more when it asks.
Want this working inside your team?
It starts with one conversation about your workflow.