GitHub
Lingphi AI / Lingent

Lingent Documentation

Web documentation, setup guides, security notes, and support links for Lingent.

Read docs Create an issue

Current product line

v0.23.0

Model access

user provider / localhost gateway

Concepts

Lingent is organized around a small set of runtime concepts.

Orchestrator

The orchestrator receives the user's goal, loads relevant memory and page context, decides which tools or agents to call, and synthesizes the result. It is configured in Settings, including model, temperature, max turns, enabled tools, and approval behavior.

Browser Pilot

Browser Pilot is the autonomous browser agent. It reads a semantic snapshot of the page, acts through browser tools, and refreshes its perception after page-changing actions. The goal is to operate the active web workflow without making the user manually choose selectors or copy page content.

Browser Pilot can:

  • Read page text.
  • Snapshot interactive elements.
  • Click, type, select, scroll, and navigate.
  • Extract tables.
  • Use vision grounding when an element is visual or missing from the DOM

snapshot.

  • Manage autonomous session tabs.

Platform agents

Platform agents are specialized workers for systems such as GitHub, Jira, Azure, SharePoint, external search, form prefill, and browser tasks. The orchestrator delegates platform-specific work to them instead of answering from memory about live systems.

Writing Pad

Writing Pad is a drafting surface with standalone, side-panel, and floating modes. It supports editable prompt actions such as polish, professional rewrite, concise rewrite, expand, summarize, reply, and match tone. It can attach current page context so replies and rewrites stay grounded in what the user is reading.

Activity ledger

The activity ledger records agent runs. It captures the goal, trigger, tool steps, approvals, redacted arguments, truncated results, model usage, write receipts, and final message. This is the primary review surface for understanding what Lingent did.

User-defined platforms

Lingent can extend beyond built-in platforms through:

  • Marketplace manifests for declarative HTTP API integrations.
  • OpenAPI specs.
  • MCP servers.
  • Content-script bridges for page-native workflows.

Each extension path should be configured visibly in Settings so users can see what a platform can do before delegating work to it.