Skip to main content

The Gram Agent

The gram agent is Appgrammar's built-in coding agent. It's what runs inside the mesh daemon by default, and it's why your mesh nodes work the moment they come online — no separate CLI install, no vendor login, no commercial-licensing friction.

Why a built-in agent​

Mesh nodes need an agent that starts with the VM, runs unattended, and respects the credentials you control. The gram agent:

  • Is model-agnostic. It talks to Anthropic, OpenAI, Google, Together, Nebius, local LM Studio, or any OpenAI-compatible endpoint.
  • Uses your keys. You configure LLM API keys per mesh (or per node). See LLM Keys.
  • Is token-efficient. Prompt caching, context filtering, and automatic transcript condensation let it run long sessions without runaway spend.
  • Is mesh-native. All mesh MCP tools are registered directly inside the agent — no extra network hop between agent and daemon.

Capabilities​

  • Built-in tools — file read/write/edit, shell, glob, grep, web fetch, and subagent spawn — everything you expect from a modern coding agent.
  • MCP client — connect to any MCP server your team already uses; the gram agent consumes them alongside its built-in tools.
  • Inspector chain — every tool call is vetted for security, permissions, and loop detection before it runs.
  • Session persistence — sessions resume across restarts; git auto-commit after edits means nothing is lost.
  • Subagent pool — spawn focused subagents (general, explore, plan) for parallel work.
  • Architect / editor split — optional dual-model pattern: a stronger model plans, a faster model edits.

When another agent makes sense​

The mesh daemon also supports Claude Code, Codex, and Gemini CLI as the in-session agent. Pick one of those when:

  • Your team is already standardized on that product and you want to match its UX exactly.
  • You need a feature only available in that vendor's agent.

In both cases, the mesh daemon itself stays the same — it's always the gram agent's daemon runtime. The choice is about which agent a developer's session runs.

Using the agent locally​

The gram agent is also available outside the mesh as a standalone CLI (gram), so your developers can use the same tool locally that runs on the mesh. Same inspectors, same tool surface, same memory model.

Next​