Core concepts

Tools

The tools Morbium agents use to read and edit files, run commands, search, design boards and 3D models, build parts lists, and source components.

A tool is an action an agent can take. When you ask for something, the agent decides which tools to use and in what order. Which tools an agent may use is controlled by permissions.

General tools

These are the everyday tools agents use to work with your project:

  • read opens a file.
  • write creates a new file.
  • edit and apply_patch change an existing file.
  • list, glob, and grep explore and search the project.
  • bash runs a shell command in your project (this is also the terminal).
  • task delegates a focused job to a subagent.
  • webfetch reads a web page, and websearch searches the web for current information.
  • todowrite keeps a checklist for multi-step work.
  • question asks you to choose when a decision is yours to make.
  • skill loads a skill, a packaged set of instructions for a task.

Hardware tools

These power Morbium's hardware work:

  • validate_circuit renders the active board and reports compile errors, unconnected traces, missing footprints, and placement problems. The board designer runs this in a loop until the board is clean.
  • show_pcb brings a specific board into the PCB viewer.
  • read_pcb reads a board's real physical dimensions: outline size and thickness, mounting-hole positions, connectors, and the height of each part. The fabricator uses this to size enclosures.
  • build_fabrication compiles a 3D model and reports its part count, triangle count, bounding box, and any warnings.
  • show_fabrication brings a 3D model into the Fabricate viewer.
  • update_bom extracts the bill of materials from a board into a CSV.
  • set_bom_sourcing records vendor, price, and stock for a part.
  • search_registry searches a parts catalog for components and higher-level building blocks.
  • inspect_component returns a part's authoritative pin map and usage details.

Enabling and disabling tools

Tools are gated by permissions, so you can allow, ask before, or deny any of them, globally or per agent. For example, the Plan agent has all editing tools denied, which is what makes it read-only. See Permissions.

Custom tools

You can add your own tools that the AI can call, through plugins or local tool files in your project. This is advanced; most users never need it.

Next steps