smrt
Open the smrt source on GitHub Switch to dark color scheme

Tooling · 0.55.16

Build the app. Inspect the workspace. Operate the right surface.

This section covers the systems developers and coding agents work with. It also explains the runtime surfaces that application agents use. Those surfaces aren't interchangeable. Every claim in this section was checked against the released 0.55.16 packages.

Three audiences

Developers

Developers create projects, change models, generate artifacts, run tests and apply migrations. CI runs the same project checks and generation commands. These actions can write files or change the configured development database.

Coding agents

Coding agents inspect source, manifests, package contracts and generated knowledge. Development MCP is read-only. If an agent can also edit the repository, that permission comes from the coding-agent client.

Application agents

Application agents use generated local MCP, hosted application MCP or WebMCP. Their calls can operate live data, and they stay inside the application authentication, tenant, permission and field-policy boundaries.

Separate surfaces

SurfacePrimary audienceBoundaryReach for it when
CLI, templates, and scannerDevelopers and CIRuns in the local workspace. Commands can create files, generate artifacts, inspect manifests, and apply migrations to the configured database.You need to start an app, change its model, generate interfaces, verify it, or operate its development database.
Knowledge commandsDevelopers and coding agentsReads workspace files, generated knowledge, installed-package contracts, and git history. It does not inspect live application data.You need a deterministic index, freshness result, change report, or review and architecture context.
Development MCPCoding agentsRuns as a local, read-only stdio server. It inspects the workspace and installed packages but cannot access the running application.A coding agent needs structured discovery, diagnostics, generation output, or review context through MCP.
Generated local MCPLocal application agentsRuns beside the application and operates live data. It gets credentials from its environment and has no per-request principal, so it stays local.A trusted application agent on the same machine must use generated model operations.
Hosted application MCPRemote application agentsRuns as a stateless HTTP route. A gateway terminates authorization, and the application resolves a principal for each request.A remote application agent needs permitted operations against a deployed application.
WebMCPBrowser-session application agentsRegisters tools in the browser page and calls the generated REST surface as the signed-in page user. It is not a separate server.An application agent in the browser must use actions that the current page exposes.
Agent PluginCoding-agent clientsPackages the same local Development MCP server with manifests, schemas, and skills. The client keeps credentials outside the package.A compatible coding-agent client can discover the development integration from a package.

Pages in this section