NOT A PET

The company appears to be a solo project named "NOT A PET", self-described as an AI-powered desktop character that lives on your Mac, interacts with you via voice and emotion, and uses existing AI subscriptions (GPT-5.6, Claude) as its "brains". The author states this is built using Swift/AppKit, with no API keys required, and supports shared memory between different AI models.

What changed: The project is a hackathon submission, not yet a commercial product or service. It represents an experimental integration of personal AI agents with desktop interaction paradigms, using existing subscriptions rather than proprietary APIs.

The single most important open question: Is there any evidence of user adoption, revenue, or traction beyond the author's own development and demonstration?

Note: This analysis is based entirely on the self-reported project description provided by the caller. No third-party verification, archived data, or independent sources are available. All claims are attributed to the author’s own account.

The description states that NOT A PET is a desktop application for macOS where:

• A user-defined character lives on the screen.
• It interacts with the user via voice (using VOICEVOX) and emotion portraits.
• It can switch between AI models (GPT-5.6 and Claude) without losing memory.
• The app uses existing AI subscriptions directly through CLI tools (headless codex exec, claude -p).
• Characters are created from single images using Codex (hatch-pet), generating animated sprites and expressions.

Inference: The product is a prototype or proof-of-concept built for a hackathon, not yet a commercial offering. It integrates AI agents into desktop interaction patterns, but lacks any evidence of real-world usage or monetization.

The author positions NOT A PET as:

• An alternative to "desktop pets" — which they describe as “adorable — and useless.”
• A way to give life to one’s own character using existing AI tools.
• A seamless experience across multiple AI models with shared memory.
• A tool that allows users to interact with their AI agents in a more natural, embodied way.

Inference: The positioning is aspirational and conceptual. It reflects a vision of personal AI companionship but does not indicate any actual market traction or customer feedback.

The description does not name specific customers or personas. However, it implies:

• Users who have existing subscriptions to AI models like GPT-5.6 and Claude.
• People interested in creative expression through digital characters.
• Developers or early adopters of AI agent interfaces.

Inference: There is no evidence of a defined ICP beyond the author’s own use case. No segmentation, targeting, or customer interviews are mentioned.

There is no mention of pricing, monetization, or business model in the description.

Inference: The project appears to be non-commercial at this stage. It was submitted as a hackathon entry and lacks any indication of how it might generate revenue.

The author states:

• Built with Swift/AppKit.
• Single-file app with transparent always-on-top panel.
• Uses CALayer for sprite playback at 60fps.
• Implements Carbon global hotkey, menu-bar residency, radial menu.
• Integrates headless CLI modes (codex exec / claude -p) to access AI models.
• Memory system uses transcript.jsonl and notes.md files.

Inference: The technical stack is native macOS development. The architecture shows some sophistication in handling AI integration and UI animation, but again, no evidence of production deployment or scalability.

No traction data is provided. The project is described as:

• A hackathon submission.
• Not yet a commercial product.
• Demonstrated via video or screenshots (not detailed).

Inference: There is no evidence of users, customers, or adoption beyond the author’s own work. No metrics, usage data, or feedback are included.

The description does not reference competitors or similar products. It does not compare itself to existing AI desktop tools, chatbots, or character-based interfaces.

Inference: No competitive positioning or market analysis is evident. The project seems isolated in its concept without a clear understanding of the broader landscape.

• Solo development: Only one team member listed (阳树 渡辺). This raises concerns about scalability and long-term maintenance.
• No commercialization plan: No pricing, monetization, or go-to-market strategy is evident.
• Unproven market demand: The concept is speculative; no evidence of user interest or validation.
• Technical feasibility: While the demo shows integration with CLI tools, real-world performance and reliability are untested.
• Lack of traction: No users, customers, or adoption metrics.

Inference: The project is experimental and not yet validated in a commercial context. It may be a creative exploration rather than a viable business opportunity.

1. What specific problem are you solving for users? Is there any user feedback or market research?
2. How do you plan to scale beyond a single developer and one prototype?
3. Have you tested this with real users, or is it purely an experimental build?
4. Are there any plans to monetize the product or offer paid features?
5. What are your long-term goals for NOT A PET? Is it intended to become a commercial product?