Feature overview

What the reviewed source describes

Lazy Coding Agent is a Free Pascal/Lazarus desktop coding workspace. This page summarizes reviewed README, help and source, with a UI screenshot from a running build.

Lazy Coding Agent window with workspaces sidebar, Markdown editor tab, Agent chat composer, and integrated terminal. — Workspace navigation, editor tabs, mode and model controls, and terminal panel in the main window.

Status distinction: “Implemented in reviewed source/docs” describes evidence in the application repository. It does not mean shipped, release-ready or verified in a running application. The README's active-integration status needs owner confirmation.

Reviewed source/docs

Workspace and editor

Documentation describes project navigation, a single-file editor, Markdown preview, chat and optional guidelines, utility and terminal panels. Panels can be shown, hidden and detached; the layout is described as persistent per workspace.

Workspace documentation topics →

Reviewed source/docs

Ask, Plan and Agent

Ask provides read/search-oriented tools; Plan can save plan Markdown; Agent can use patch, write and shell tools. By default, write paths and shell working directories stay within the workspace. A per-session option allows outside-workspace changes.

This is application-level path handling, not an operating-system sandbox. Shell and write actions run on the user's machine. Use Agent mode only when you trust the workspace and model.

Modes and tool-boundary topics →

Reviewed source/docs

Sessions and execution detail

Reviewed source/help describe multiple sessions with separate engines, saved conversation history, tool-error records and an execution detail view for recorded context and tool inputs/outputs.

The trace is not a guaranteed replay or an exposure of private hidden chain-of-thought.

Agent architecture →

Documented examples

Providers, models and images

The README names examples including Claude 3.7 Sonnet, Hermes 4 70B/405B, GPT-4o and DeepSeek R1; exact model IDs and routing depend on configuration. Help describes PNG, JPEG, WebP and GIF image attachments, up to four per message and 5 MiB each, with possible downscaling.

Model availability, capability, provider behavior and costs depend on configuration and third parties. Image understanding needs a vision-capable model.

Chat and model topics →

Caveats apply

Integrated terminal

Reviewed documentation describes a PTY terminal opened at the workspace root. Windows requires Windows 10 1809 or newer for ConPTY; Linux builds require PTY/libutil support and the documented terminal dependencies.

These are documented requirements, not a promise of identical runtime behavior on every platform.

Workspace and terminal topics →

Reviewed source/docs

Rules and preferences

README/help describe dark and light themes, per-workspace Markdown project rules injected into prompts, and debugging/Learn behavior settings. No broader plugin or extensibility claim is made.

Project rules and settings topics →

Planned work is separate

Multi-agent collaboration, execution-plan tracking, workspace knowledge/RAG and The Brain are described as future features with no backend. SQLite/vector retrieval is future planning, not a current feature. See the roadmap.

Platform packages and builds

CI publishes installers and packages for Windows, Linux (deb and AppImage), macOS (Intel and Apple Silicon), and arm64 Linux including Raspberry Pi. See downloads and build-from-source for current release assets and developer build guidance.

Maintainer evidence citations for every section are in the product feature inventory.