You land on https://kendo.dev (Kendo) for the first time. What's unclear, what makes you leave, and what would make you sign up?

Julio Weberneutral

The headline, "The issue tracker that lives in your terminal," immediately caught my attention. The integration with AI tools like Claude Code and Cursor, especially the MCP server concept, is intriguing for streamlining workflows. However, the "currently in active development" status is a bit of a flag; I need to understand what that implies for stability and feature completeness. What makes me leave is primarily the "active development" without a clearer roadmap or demo of the AI capabilities in action. To sign up, I'd need to see more concrete examples of the AI managing issues, perhaps a sandbox environment, and a clearer understanding of the product's maturity level.

Simulated interest: 50/100

Maureen Watsicaneutral

The headline "The issue tracker that lives in your terminal" immediately caught my attention. My current workflow involves constant context switching between VS Code, Slack, and my spreadsheet for logging hours, which is a significant time sink. The idea of an AI-native CLI tool for project management, especially with built-in time tracking and GitHub integration, is very appealing. However, "In active development" is a bit of a red flag for a freelancer reliant on stable tools for client work. I'd leave to dig into the docs to understand the maturity and real-world applicability of the MCP tools and CLI. If the documentation clarifies how it integrates with existing workflows and proves robust, I'd sign up for the free tier to test its effectiveness, especially the automated time logging to reduce my admin burden.

Simulated interest: 70/100

Jesse Kuprionneutral

The initial pitch about the issue tracker living in the terminal is intriguing, especially the MCP tools. However, the "in active development" notice is a bit of a concern for a production environment; I need predictability. The claim of built-in time tracking is a definite plus, as that's a separate process for us now. To sign up, I'd need to see more concrete evidence of stability and perhaps a clear path from active development to a more robust offering. I'm also unclear on how the MCP tools integrate with our existing GitHub workflows beyond just basic sync.

Simulated interest: 40/100

Vishwamitra Reddyneutral

The core proposition, "issue tracker that lives in your terminal," is intriguing. The mention of MCP tools for AI managing issues is especially relevant given my focus on workflow automation and reducing manual linking. However, the "active development" tag is a bit of a flag; I need to understand what that truly means for stability and feature completeness. I'd also want to know more about how the GitHub sync truly works – does it push/pull status automatically, or is there still a manual step? To sign up, I'd need to see a clear path to integrate it with our current GitHub Issues and Slack, and understand the specific benefits for a small, bootstrapped team like ours. Is the "free to start" offer sufficient for a 6-person team, or are there hidden costs lurking?

Simulated interest: 60/100

Farah Boschneutral

When I first land on kendo.dev, the main thing that's unclear is what "MCP tools" are. The page mentions Claude Code, Cursor, and Codex managing issues, which sounds interesting but a bit vague. What makes me leave immediately is the "Currently in active development" banner. I need reliable tools for my team, and something still in development feels risky. To make me sign up, I'd need more clarity on the MCP tools, a clearer roadmap for development, and perhaps some testimonials from teams already using it successfully. I also appreciate the EU hosting and GDPR compliance, as that's important for our studio.

Simulated interest: 40/100

Derrick Mitchellneutral

The initial impression is that Kendo offers a terminal-first approach to project management, which aligns with my preference for CLI tools and automation. However, the mention of "MCP tools" and AI assistants like Claude Code, Cursor, and Codex is unclear. I'd need to understand how these AI integrations work and if they require additional setup or are truly seamless. The fact that it's "in active development" also gives me pause; I prefer stable, mature tools for critical ops work. What would make me sign up is a clear demonstration of the CLI's capabilities, especially for incident tracking and automation, and assurances about the stability and maturity of the AI features. If the MCP tools genuinely reduce administrative overhead without introducing complexity, I'd be interested.

Simulated interest: 40/100

Carol Bayerneutral

Landing on Kendo, I'm immediately drawn to the headline about managing issues from the terminal – that sounds like it could cut down on context switching, which is a big win. The mention of AI-native tools is intriguing, especially if it can help automate updates or estimations, which is a constant headache for my team. However, the biggest unclear point for me is the 'MCP tools' and how they integrate with Claude, Cursor, and Codex. I'd need to understand that better. What might make me leave is if the setup or integration with GitHub is complex, or if the AI features are more of a gimmick than genuinely useful. To sign up, I'd need to see a clear, simple way to sync with our current GitHub workflow and a straightforward way to track time directly within the tool, as we don't currently have a dedicated time tracker.

Simulated interest: 60/100

Jeanne Mathieuneutral

Landing on Kendo, the emphasis on a terminal-based issue tracker is intriguing, especially the MCP tools for AI integration. However, the prominent "In active development" banner raises a slight concern about stability and feature completeness for a solo founder like myself. While I appreciate the idea of an AI managing tasks, I'm unsure how deeply it can integrate with my current workflow or if it would create more overhead than it solves. The built-in time tracking is a definite plus, as is the EU hosting for GDPR. To sign up, I'd need more clarity on the "active development" status and perhaps a more concrete demonstration of how the MCP tools actually save time, rather than just automate tasks I already manage.

Simulated interest: 40/100

Dayamayee Mahajanneutral

Landing on Kendo.dev, the immediate focus on terminal-based issue tracking is intriguing. The promise of integrated time tracking, especially, catches my eye as I currently manage this manually in a spreadsheet, which is quite a time sink. The AI-native aspect with MCP tools sounds advanced, but I'd need to understand how it integrates with my specific workflow and client needs – translating requirements is already a big part of my day. I might leave if I couldn't quickly grasp how the AI translates abstract client requests into actionable tickets or if the CLI felt like an unnecessary layer. To sign up, I'd want to see clear examples of how it streamlines translating client needs, especially with my distributed teams, and perhaps a more direct explanation of the AI's capabilities beyond the jargon.

Simulated interest: 60/100

Linus Lundneutral

The core proposition, an issue tracker in the terminal, is compelling and aligns with my workflow. The mention of MCP tools for AI management is intriguing, though I'd need to understand how robust that integration is and if it truly reduces manual effort without introducing new complexities. The promise of built-in time tracking and EU hosting is good. What's unclear is the maturity of the product given it's 'in active development' – how stable is it, and what's the support like? I’d need to see more concrete examples of the CLI in action beyond the basic commands shown to fully grasp its utility for complex workflows. If it proves stable and truly streamlines task management without adding overhead, I might consider trying it.

Simulated interest: 40/100