This creator - someone who describes themselves as having "very little coding experience" - built a complex application over several months using NonBioS. But what's most interesting is the complementary workflow he discovered:

• nonbios-1.13 for planning and implementing larger features
• nonbios-1.1 for debugging and discrete fault-finding tasks

The results speak for themselves. His payment system integration across three profile types:

• Using only 1.13: ~300 minutes
• Using 1.13 for building + 1.1 for debugging: 181 minutes combined for the remaining two profiles

That's a 40% reduction in development time by understanding each model's strengths.

The Pattern We're Seeing

The user describes 1.13 as "much better with analysis and full large tasks" but notes it can get "overly detailed" on smaller debugging work. Meanwhile, 1.1 excels at "smaller discrete fault finding tasks" without overthinking the problem.

This matches what we've observed internally: 1.13's enhanced autonomous capabilities and deeper analysis make it exceptional for complex feature work, but sometimes that same thoroughness can be overkill for straightforward debugging.

Why We Keep Both Models Active

This is exactly why we didn't deprecate nonbios-1.1 alongside the older models. While 1.13 represents our most advanced autonomous agent, 1.1 has a different performance profile that makes it ideal for certain tasks.

When we deprecated nonbios-1 and nonbios-1.2, it was because 1.1 had surpassed them across the board. But 1.1 and 1.13 aren't a simple progression - they're complementary tools.

The Learning Curve

The reviewer mentions something we hear often: "I found it frustrating at first but once I learned how to give instructions to the software and learned a little about the best ways to set the app up things got easier."

This is real. Working with AI agents requires learning a new skill - how to effectively communicate with and structure work for an AI collaborator. The flip side? This creator built a complex payment system across multiple profile types with minimal coding experience, learned "a significant amount about coding language and system architecture," and spent far less than hiring a developer.

Where We Go From Here

Feedback like this shapes our roadmap. We're taking notes on:

1. The context-switching challenge: The need to "bring it up to speed each time" when switching between models
2. Long conversation degradation: "Struggling with nonbios getting confused on longer chats"
3. The complementary workflow: How we might better support users who benefit from using both models

We're grateful for users who take the time to share detailed feedback like this. If you're using nonbios-1.1 and 1.13, we'd love to hear about the workflows you've discovered. What patterns are working for you? Where are the rough edges?

As always, we're building this together.

‍