01
No managed runtime
Delphi compiles directly to machine code, avoiding interpreter startup, JIT warm-up, and garbage-collector pauses in the orchestration layer.
// Why Object Pascal
Compiled. Native. Built to last.
Object Pascal gives PasClaw predictable native performance, a mature component ecosystem, strict types, and a remarkably simple deployment model.
AOT compiledSingle executableType safeMature ecosystem
02
Operational simplicity
A PasClaw deployment can be a single executable plus standard TLS libraries. That makes installation, rollback, and air-gapped operation straightforward.
03
Strong contracts
Object Pascal's explicit types help keep provider payloads, tool schemas, and lifecycle ownership understandable as an agent grows.
04
Decades of compatibility
PasClaw benefits from Delphi's stable RTL, desktop frameworks, database connectivity, and extensive native component ecosystem.
From the documentation
Technical details
Implementation notes drawn from the PasClaw repository documentation.
Native targets
The documented build matrix covers Linux x86_64 and aarch64 with FPC, macOS on Intel and Apple Silicon, and Windows x64 with Delphi 12 / RAD Studio.
- Windows ARM64 is available as a cross-build target.
- The project also documents a compact Docker deployment.
- Indy provides the networking layer in Delphi and is vendored for FPC builds.
Embeddable components
TPasClawAgent and TPasClawServer are TComponent descendants designed to fit existing VCL and FireMonkey applications.
- Components can be created in code or placed in the form designer.
- Published properties expose configuration through familiar Delphi tooling.
- The same core can run inside a desktop app, CLI, or service process.
Source documentation
Common questions
Frequently asked questions
Keep exploring
See how the rest of PasClaw fits together.