Glossary

Feedback and AI glossary

Plain-English definitions for website feedback, developer context, the Model Context Protocol and AI coding agents.

AI coding agent

An AI coding agent plans, edits, tests, and submits code changes from natural-language development tasks.

A bug report documents a software problem with steps, context, expected behavior, and evidence so developers can reproduce and fix it.

A console error is a browser-reported runtime, loading, or security problem that helps developers find and fix broken site behavior.

Developer context is the technical detail needed to understand, reproduce, and fix an issue in a codebase.

Error monitoring tracks runtime failures, alerts teams, and provides context needed to reproduce, prioritize, and fix bugs in production.

A feedback loop is the cycle of observing results, learning from them, and using that information to improve a system or product.

An issue tracker is a system for recording, prioritizing, assigning, and resolving bugs, tasks, feature requests, and technical work.

Model Context Protocol (MCP) is a standard for connecting AI models to tools, data, and developer workflows.

A network request is a browser or app call to another resource, such as an API, image, script, or page, over HTTP or HTTPS.

A regression is when previously working software breaks after a change, often due to code, dependency, config, or data updates.

Root cause analysis identifies the real source of a bug or incident so teams can fix it, not just patch symptoms.

Session replay records a user's browser session so teams can inspect clicks, navigation, errors, and UI behavior during debugging.

Visual feedback is UI response that shows users what happened, what is happening, or what needs attention.

Website annotation lets teams mark up live pages with comments, context, screenshots, and bug details tied to specific UI elements.

Add one script tag and give your AI agent the context it has been missing. Free while we grow.