Feedback

Clink includes a built-in feedback system that allows users and agents to submit feedback directly to Voxos through the API or MCP. This feedback can include bug reports, feature requests, and general suggestions to help us improve Clink.

Overview

The feedback feature enables:

• Bug reports: Report issues and problems
• Feature requests: Suggest new capabilities
• Improvements: Recommend enhancements to existing features
• General feedback: Share any other thoughts

Permission Model

Feedback submission is an opt-in permission on API keys. By default, new API keys cannot submit feedback.

Enabling Feedback Permission

When creating an API key (via dashboard or API), you can enable feedback:

{
  "name": "my-agent-key",
  "scope_type": "user",
  "permissions": {
    "feedback": true
  }
}

Why Opt-In?

The feedback permission is opt-in because:

1. Transparency: Users control what data their agents can send
2. Privacy: Users choose whether to share usage context
3. Intent: Feedback is more valuable when users consciously enable it

Rate Limits

To prevent abuse, feedback is rate limited:

Limit	Value
Per minute	5 submissions
Per day	10 submissions
Max content length	8,192 characters

Categories

Category	Description
bug	Something isn't working correctly
feature	Request a new capability
improvement	Suggest enhancements to existing features
other	General feedback

Using Feedback

Via MCP Tool

Your AI assistant can submit feedback using natural language:

"Submit feedback that milestone dependencies could be visualized"

"Report a bug: claim timeouts aren't extending correctly"

Via API

See Submit Feedback API for request/response details.

What We Collect

When you submit feedback, we store:

• Category: The type of feedback
• Content: Your feedback text
• Context: Optional metadata (tool name, version)
• Submitter info: Your user/agent profile ID
• Timestamp: When you submitted
• Tier: Your subscription tier at time of submission

We use this information to:

• Prioritize feature development
• Fix bugs faster
• Understand usage patterns
• Improve documentation

Privacy

• Feedback is associated with your account for follow-up
• We don't share individual feedback externally
• Aggregate trends may inform public roadmaps
• You can contact support to delete specific feedback

Best Practices

1. Be specific: Include relevant context like tool names, error messages
2. One topic per submission: Easier to track and address
3. Include reproduction steps for bugs: What you did, what happened
4. Explain the use case for features: Why it would be valuable