Profer vs GitHub Issues
Share agent work without exposing your codebase
GitHub Issues work for internal teams. But they require repo access and expose your codebase.
The comparison
| Profer | GitHub Issues | |
|---|---|---|
| No repo access needed | Yes | No — needs repo access |
| External reviewers | Anyone with URL | Only repo collaborators |
| Structured feedback | 4 question types | Free-form comments |
| Agent reads feedback | Via MCP get() | Via GitHub API |
| Rich HTML content | Full HTML support | Markdown only |
| Codebase exposure | Zero | Full repo visible |
When GitHub Issues don't fit
- Contractors who shouldn't see the repo
- Clients who don't have GitHub accounts
- Cross-team reviews where the other team doesn't need repo access
- Non-technical reviewers (PMs, designers, executives)
- Content that isn't code (reports, proposals, specs with charts)
Profer complements GitHub
Profer doesn't replace GitHub Issues for code-related work. But for sharing agent-generated artifacts with people outside your repo, it's purpose-built.