Feature Request: Add App Identification to Feedback Output

[harshmathur-rzp]

Problem

When using Agentation in a monorepo or when running multiple applications, the copied feedback output doesn't specify which application the feedback is from. This makes it difficult to identify the source when working with multiple apps or when sharing feedback with team members.

Current Behavior

The copied output format looks like this:

## Page Feedback: /
**Viewport:** 1701×861

### 1. paragraph: "Some text content..."
**Location:** .flex > .flex > .flex > p
**Feedback:** Some feedback about the element

The output only shows the page path (/) but doesn't indicate which application is running (e.g., "App A", "App B", etc.).

Expected Behavior

The output should include app identification, either:

1. Option A: As a prop to the <Agentation /> component:

   <Agentation appName="My App" />

2. Option B: Automatically detected from document.title or meta tags

3. Option C: Customizable via a configuration object

The output would then look like:

## Page Feedback: / (My App)
**Viewport:** 1701×861
...

Or:

## Page Feedback: /
**App:** My App
**Viewport:** 1701×861
...

Use Case

We have multiple React applications in our monorepo. When copying feedback from Agentation, it's unclear which app the feedback refers to, especially when:

• Sharing feedback with team members
• Reviewing feedback later
• Working with multiple apps simultaneously
• Integrating feedback into project management tools

Attempted Solutions

We've tried several approaches that didn't work:

1. Props: Tried passing appName, appId, key, etc. to the component
2. Document Title: Set document.title - not reflected in output
3. Meta Tags: Added meta tags - not used
4. Data Attributes: Added data attributes to root element - not captured

Suggested Implementation

We suggest adding an optional appName prop (or similar) to the Agentation component:

interface AgentationProps {
  appName?: string;
  // ... other existing props
}

Then include it in the markdown output header. This would be a minimal, non-breaking change that provides the flexibility needed for multi-app scenarios.

Environment

• Agentation version: 1.0.0
• React version: 18.3.1
• Browser: Desktop (Chrome, Firefox, Safari)

Additional Context

This feature would be particularly valuable for:

• Monorepos with multiple applications
• Teams working on multiple projects
• Documentation and feedback tracking
• Integration with AI coding assistants that need context about which codebase to modify

Thank you for considering this feature request!

[benjitaylor]

Good idea - not in v2 but would be useful for monorepos. Keeping this open.

[harshmathurx]

I'd be happy to create a PR for this

[prakersh]

onUI handles this by capturing page URL and metadata alongside each annotation, so you always know which app/page feedback came from. It's a free, open-source browser extension with a local MCP server that makes this context available to AI agents programmatically.