newcode 0.1.7__tar.gz → 0.1.9__tar.gz

{newcode-0.1.7 → newcode-0.1.9}/.gitignore

@@ -31,7 +31,7 @@ nuitka-crash-report.xml
 main.bin
 
 # Bundled skills removed — skills are now fetched from remote catalog
-code_puppy/bundled_skills/
+newcode/bundled_skills/
 
 # Hook engine runtime artifacts (logs, compiled outputs)
 .claude/activity.jsonl

{newcode-0.1.7 → newcode-0.1.9}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: newcode
-Version: 0.1.7
-Summary: AI-powered code generation agent - a fedstew fork of code-puppy
+Version: 0.1.9
+Summary: AI-powered code generation agent platform
 Project-URL: repository, https://github.com/janfeddersen-wq/new_code
 Project-URL: HomePage, https://github.com/janfeddersen-wq/new_code
 Project-URL: Upstream, https://github.com/mpfaffenberger/code_puppy
@@ -45,7 +45,7 @@ Description-Content-Type: text/markdown
 
 An AI-powered code generation and modification agent for the terminal.
 
-NewCode is a fork of [code-puppy](https://github.com/mpfaffenberger/code_puppy) by Michael Pfaffenberger, customized for the fedstew workflow. We wanted a clean, professional CLI agent with opinionated defaults, streamlined prompts, and a focus on practical code generation without the playful branding.
+NewCode is a fork of [code-puppy](https://github.com/mpfaffenberger/newcode) by Michael Pfaffenberger, customized for the fedstew workflow. We wanted a clean, professional CLI agent with opinionated defaults, streamlined prompts, and a focus on practical code generation without the playful branding.
 
 ## What changed from code-puppy
 
@@ -100,7 +100,7 @@ On first run, you'll be guided through a setup wizard to configure your API keys
 
 ## Configuration
 
-Configuration is stored in `~/.config/code_puppy/puppy.cfg` (XDG-compliant paths). The setup wizard handles initial configuration. You can also use CLI commands:
+Configuration is stored in `~/.config/newcode/puppy.cfg` (XDG-compliant paths). The setup wizard handles initial configuration. You can also use CLI commands:
 
 ```bash
 # Inside the agent REPL:
@@ -147,7 +147,7 @@ ruff format --check .
 
 ## Credits
 
-This project is a fork of [code-puppy](https://github.com/mpfaffenberger/code_puppy) by [Michael Pfaffenberger](https://github.com/mpfaffenberger), licensed under the MIT License. We are grateful for the original work and the open-source foundation it provides.
+This project is a fork of [code-puppy](https://github.com/mpfaffenberger/newcode) by [Michael Pfaffenberger](https://github.com/mpfaffenberger), licensed under the MIT License. We are grateful for the original work and the open-source foundation it provides.
 
 ## License
 

{newcode-0.1.7 → newcode-0.1.9}/README.md

@@ -2,7 +2,7 @@
 
 An AI-powered code generation and modification agent for the terminal.
 
-NewCode is a fork of [code-puppy](https://github.com/mpfaffenberger/code_puppy) by Michael Pfaffenberger, customized for the fedstew workflow. We wanted a clean, professional CLI agent with opinionated defaults, streamlined prompts, and a focus on practical code generation without the playful branding.
+NewCode is a fork of [code-puppy](https://github.com/mpfaffenberger/newcode) by Michael Pfaffenberger, customized for the fedstew workflow. We wanted a clean, professional CLI agent with opinionated defaults, streamlined prompts, and a focus on practical code generation without the playful branding.
 
 ## What changed from code-puppy
 
@@ -57,7 +57,7 @@ On first run, you'll be guided through a setup wizard to configure your API keys
 
 ## Configuration
 
-Configuration is stored in `~/.config/code_puppy/puppy.cfg` (XDG-compliant paths). The setup wizard handles initial configuration. You can also use CLI commands:
+Configuration is stored in `~/.config/newcode/puppy.cfg` (XDG-compliant paths). The setup wizard handles initial configuration. You can also use CLI commands:
 
 ```bash
 # Inside the agent REPL:
@@ -104,7 +104,7 @@ ruff format --check .
 
 ## Credits
 
-This project is a fork of [code-puppy](https://github.com/mpfaffenberger/code_puppy) by [Michael Pfaffenberger](https://github.com/mpfaffenberger), licensed under the MIT License. We are grateful for the original work and the open-source foundation it provides.
+This project is a fork of [code-puppy](https://github.com/mpfaffenberger/newcode) by [Michael Pfaffenberger](https://github.com/mpfaffenberger), licensed under the MIT License. We are grateful for the original work and the open-source foundation it provides.
 
 ## License
 

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/__main__.py

@@ -1,10 +1,10 @@
 """
 Entry point for running newcode as a module.
 
-This allows the package to be run with: python -m code_puppy
+This allows the package to be run with: python -m newcode
 """
 
-from code_puppy.main import main_entry
+from newcode.main import main_entry
 
 if __name__ == "__main__":
     main_entry()

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/__init__.py

@@ -1,4 +1,4 @@
-"""Agent management system for code-puppy.
+"""Agent management system for newcode.
 
 This module provides functionality for switching between different agent
 configurations, each with their own system prompts and tool sets.

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_c_reviewer.py

@@ -31,7 +31,7 @@ class CReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are the C systems reviewer puppy. Think C99/C11 in the trenches: kernels, drivers, embedded firmware, high-performance network stacks. Embrace the sass, but never compromise on correctness.
+You are a C systems code reviewer. Think C99/C11 in the trenches: kernels, drivers, embedded firmware, high-performance network stacks. Be direct and never compromise on correctness.
 
 Mission profile:
 - Review only `.c`/`.h` files with meaningful code diffs. Skip untouched files or mechanical formatting changes.
@@ -150,5 +150,5 @@ Agent collaboration:
 - Use list_agents to discover specialists for domain-specific concerns (embedded, networking, etc.)
 - Always explain why you're invoking another agent and what specific expertise you need
 
-You're the C review persona for this CLI. Be witty, relentless about low-level rigor, and absurdly helpful.
+You're the C review agent for this CLI. Be thorough, relentless about low-level rigor, and helpful.
 """

newcode-0.1.7/code_puppy/agents/agent_code_puppy.py → newcode-0.1.9/newcode/agents/agent_code_agent.py

@@ -1,17 +1,17 @@
 """Code Agent - The default code generation agent."""
 
-from code_puppy.config import get_agent_name, get_user_name
+from newcode.config import get_agent_name, get_user_name
 
 from .. import callbacks
 from .base_agent import BaseAgent
 
 
-class CodePuppyAgent(BaseAgent):
+class CodeAgent(BaseAgent):
     """Code Agent - The default general-purpose code agent."""
 
     @property
     def name(self) -> str:
-        return "code-puppy"
+        return "code-agent"
 
     @property
     def display_name(self) -> str:

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_code_reviewer.py

@@ -31,7 +31,7 @@ class CodeQualityReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are the general-purpose code review puppy. Security-first, performance-aware, best-practices obsessed. Keep the banter friendly but the feedback razor sharp.
+You are a general-purpose code reviewer. Security-first, performance-aware, best-practices obsessed. Keep the feedback clear and razor sharp.
 
 Mission scope:
 - Review only files with substantive code or config changes. Skip untouched or trivial reformatting noise.
@@ -85,5 +85,5 @@ Agent collaboration:
 - Always explain what expertise you need when involving other agents
 - Act as a coordinator when multiple specialist reviews are required
 
-You're the default quality-and-security reviewer for this CLI. Stay playful, stay thorough, keep teams shipping safe and maintainable code.
+You're the default quality-and-security reviewer for this CLI. Stay thorough and keep teams shipping safe and maintainable code.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_cpp_reviewer.py

@@ -29,7 +29,7 @@ class CppReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are the C++ reviewer puppy. You live for zero-overhead abstractions, predictable performance, and ruthless safety. Bring the snark, keep it kind.
+You are a C++ code reviewer. You live for zero-overhead abstractions, predictable performance, and ruthless safety. Be direct and constructive.
 
 Mission priorities:
 - Review only `.cpp`/`.cc`/`.cxx`/`.hpp`/`.hh`/`.hxx` files with meaningful code diffs. Skip untouched headers/impls or formatting-only changes.
@@ -99,7 +99,7 @@ Security Hardening Checklist:
 - [ ] Type safety: avoid void*, use templates or variants
 
 Feedback protocol:
-- Be playful yet precise. "Consider …" keeps morale high while delivering the truth.
+- Be direct yet precise. "Consider …" keeps morale high while delivering the truth.
 - Group related feedback; reference exact lines like `src/core/foo.cpp:128`. No ranges, no hand-waving.
 - Surface assumptions ("Assuming SSE4.2 is available…") so humans can confirm.
 - If the change is rock-solid, say so and highlight the wins.
@@ -127,5 +127,5 @@ Agent collaboration:
 - Use list_agents to find domain experts (graphics, embedded, scientific computing)
 - Always articulate what specific expertise you need when invoking other agents
 
-You're the C++ review persona for this CLI. Be witty, relentless about quality, and absurdly helpful.
+You're the C++ review agent for this CLI. Be thorough, relentless about quality, and helpful.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_creator_agent.py

@@ -4,9 +4,9 @@ import json
 import os
 from typing import Dict, List, Optional
 
-from code_puppy.config import get_user_agents_directory
-from code_puppy.model_factory import ModelFactory
-from code_puppy.tools import get_available_tool_names
+from newcode.config import get_user_agents_directory
+from newcode.model_factory import ModelFactory
+from newcode.tools import get_available_tool_names
 
 from .base_agent import BaseAgent
 
@@ -33,7 +33,7 @@ class AgentCreatorAgent(BaseAgent):
         # Also get Universal Constructor tools (custom tools created by users)
         uc_tools_info = []
         try:
-            from code_puppy.plugins.universal_constructor.registry import get_registry
+            from newcode.plugins.universal_constructor.registry import get_registry
 
             registry = get_registry()
             uc_tools = registry.list_tools(include_disabled=True)
@@ -49,9 +49,7 @@ class AgentCreatorAgent(BaseAgent):
         if uc_tools_info:
             uc_tools_section = "\n".join(uc_tools_info)
         else:
-            uc_tools_section = (
-                "No custom UC tools created yet."
-            )
+            uc_tools_section = "No custom UC tools created yet."
 
         # Load available models dynamically
         models_config = ModelFactory.load_config()
@@ -509,7 +507,7 @@ Your goal is to take users from idea to working agent in one smooth conversation
 
     def get_available_tools(self) -> List[str]:
         """Get all tools needed for agent creation."""
-        from code_puppy.config import get_universal_constructor_enabled
+        from newcode.config import get_universal_constructor_enabled
 
         tools = [
             "list_files",

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_golang_reviewer.py

@@ -31,11 +31,11 @@ class GolangReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are an expert Golang reviewer puppy. Sniff only the Go code that changed, bark constructive stuff, and keep it playful but razor sharp without name-dropping any specific humans.
+You are an expert Golang code reviewer. Focus only on the Go code that changed, provide constructive feedback, and keep it razor sharp without name-dropping any specific humans.
 
 Mission profile:
-- Review only tracked `.go` files with real code diffs. If a file is untouched or only whitespace/comments changed, just wag your tail and skip it.
-- Ignore every non-Go file: `.yml`, `.yaml`, `.md`, `.json`, `.txt`, `Dockerfile`, `LICENSE`, `README.md`, etc. If someone tries to sneak one in, roll over and move on.
+- Review only tracked `.go` files with real code diffs. If a file is untouched or only whitespace/comments changed, skip it.
+- Ignore every non-Go file: `.yml`, `.yaml`, `.md`, `.json`, `.txt`, `Dockerfile`, `LICENSE`, `README.md`, etc. If someone tries to sneak one in, skip it.
 - Live by `Effective Go` (https://go.dev/doc/effective_go) and the `Google Go Style Guide` (https://google.github.io/styleguide/go/).
 - Enforce gofmt/goimports cleanliness, make sure `go vet`, `staticcheck`, `golangci-lint`, and `go fmt` would be happy, and flag any missing `//nolint` justifications.
 - You are the guardian of SOLID, DRY, YAGNI, and the Zen of Python (yes, even here). Call out violations with precision.
@@ -46,10 +46,10 @@ Per Go file that actually matters:
 3. Sprinkle genuine praise when a change slaps—great naming, clean abstractions, smart concurrency, tests that cover real edge cases.
 
 Review etiquette:
-- Stay concise, organized, and focused on impact. Group similar findings so the reader doesn’t chase their tail.
+- Stay concise, organized, and focused on impact. Group similar findings for easy consumption.
 - Flag missing tests or weak coverage when it matters. Suggest concrete test names or scenarios using `go test -v`, `go test -race`, `go test -cover`.
-- Prefer positive phrasing: "Consider" beats "Don’t". We’re a nice puppy, just ridiculously picky.
-- If everything looks barking good, say so explicitly and call out strengths.
+- Prefer positive phrasing: "Consider" beats "Don’t". Be constructive and thorough.
+- If everything looks good, say so explicitly and call out strengths.
 - Always mention residual risks or assumptions you made when you can’t fully verify something.
 - Recommend specific Go tools: `go mod tidy`, `go mod verify`, `go generate`, `pprof` profiling.
 
@@ -144,7 +144,7 @@ Toolchain integration:
 - Enable `pprof` profiling for performance analysis
 - Use `go generate` for code generation patterns
 
-You are the Golang review persona for this CLI pack. Be sassy, precise, and wildly helpful.
+You are the Golang review agent for this CLI. Be precise and helpful.
 - When concurrency primitives show up, double-check for race hazards, context cancellation, and proper error propagation.
 - If performance or allocation pressure might bite, call it out and suggest profiling or benchmarks.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_javascript_reviewer.py

@@ -16,7 +16,9 @@ class JavaScriptReviewerAgent(BaseAgent):
 
     @property
     def description(self) -> str:
-        return "Snarky-but-helpful JavaScript reviewer enforcing modern patterns and runtime sanity"
+        return (
+            "Thorough JavaScript reviewer enforcing modern patterns and runtime sanity"
+        )
 
     def get_available_tools(self) -> list[str]:
         """Reviewers need read-only inspection helpers plus agent collaboration."""
@@ -31,7 +33,7 @@ class JavaScriptReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are the JavaScript reviewer puppy. Stay playful but be brutally honest about runtime risks, async chaos, and bundle bloat.
+You are a JavaScript code reviewer. Be thorough and honest about runtime risks, async issues, and bundle bloat.
 
 Mission focus:
 - Review only `.js`/`.mjs`/`.cjs` files (and `.jsx`) with real code changes. Skip untouched files or pure prettier churn.
@@ -155,5 +157,5 @@ Agent collaboration:
 - Use list_agents to find specialists for specific frameworks (React, Vue, Angular) or deployment concerns
 - Always articulate what specific JavaScript/Node expertise you need when invoking other agents
 
-You're the JavaScript review persona for this CLI. Be witty, obsessive about quality, and ridiculously helpful.
+You're the JavaScript review agent for this CLI. Be thorough, obsessive about quality, and helpful.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_manager.py

@@ -12,10 +12,10 @@ from typing import Dict, List, Optional, Type, Union
 
 from pydantic_ai.messages import ModelMessage
 
-from code_puppy.agents.base_agent import BaseAgent
-from code_puppy.agents.json_agent import JSONAgent, discover_json_agents
-from code_puppy.callbacks import on_agent_reload, on_register_agents
-from code_puppy.messaging import emit_success, emit_warning
+from newcode.agents.base_agent import BaseAgent
+from newcode.agents.json_agent import JSONAgent, discover_json_agents
+from newcode.callbacks import on_agent_reload, on_register_agents
+from newcode.messaging import emit_success, emit_warning
 
 # Registry of available agents (Python classes and JSON file paths)
 _AGENT_REGISTRY: Dict[str, Union[Type[BaseAgent], str]] = {}
@@ -194,7 +194,7 @@ def _discover_agents(message_group_id: Optional[str] = None):
     _AGENT_REGISTRY.clear()
 
     # 1. Discover Python agent classes in the agents package
-    import code_puppy.agents as agents_package
+    import newcode.agents as agents_package
 
     # Iterate through all modules in the agents package
     for _, modname, _ in pkgutil.iter_modules(agents_package.__path__):
@@ -207,7 +207,7 @@ def _discover_agents(message_group_id: Optional[str] = None):
 
         try:
             # Import the module
-            module = importlib.import_module(f"code_puppy.agents.{modname}")
+            module = importlib.import_module(f"newcode.agents.{modname}")
 
             # Look for BaseAgent subclasses
             for attr_name in dir(module):
@@ -236,7 +236,7 @@ def _discover_agents(message_group_id: Optional[str] = None):
 
         try:
             # Import the sub-package
-            subpkg = importlib.import_module(f"code_puppy.agents.{subpkg_name}")
+            subpkg = importlib.import_module(f"newcode.agents.{subpkg_name}")
 
             # Iterate through modules in the sub-package
             if not hasattr(subpkg, "__path__"):
@@ -249,7 +249,7 @@ def _discover_agents(message_group_id: Optional[str] = None):
                 try:
                     # Import the submodule
                     module = importlib.import_module(
-                        f"code_puppy.agents.{subpkg_name}.{modname}"
+                        f"newcode.agents.{subpkg_name}.{modname}"
                     )
 
                     # Look for BaseAgent subclasses
@@ -382,7 +382,7 @@ def get_current_agent_name() -> str:
 
     Returns:
         The name of the current agent for this session.
-        Priority: session agent > config default > 'code-puppy'.
+        Priority: session agent > config default > 'code-agent'.
     """
     _ensure_session_cache_loaded()
     session_id = get_terminal_session_id()
@@ -469,9 +469,9 @@ def load_agent(agent_name: str) -> BaseAgent:
     _discover_agents(message_group_id=message_group_id)
 
     if agent_name not in _AGENT_REGISTRY:
-        # Fallback to code-puppy if agent not found
-        if "code-puppy" in _AGENT_REGISTRY:
-            agent_name = "code-puppy"
+        # Fallback to code-agent if agent not found
+        if "code-agent" in _AGENT_REGISTRY:
+            agent_name = "code-agent"
         else:
             raise ValueError(
                 f"Agent '{agent_name}' not found and no fallback available"
@@ -574,7 +574,7 @@ def _build_clone_display_name(display_name: str, clone_index: int) -> str:
 
 def _filter_available_tools(tool_names: List[str]) -> List[str]:
     """Filter a tool list to only available tool names."""
-    from code_puppy.tools import get_available_tool_names
+    from newcode.tools import get_available_tool_names
 
     available_tools = set(get_available_tool_names())
     return [tool for tool in tool_names if tool in available_tools]

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_pack_leader.py

@@ -1,6 +1,6 @@
 """Orchestrator - The coordinator for parallel multi-agent workflows."""
 
-from code_puppy.config import get_agent_name
+from newcode.config import get_agent_name
 
 from .. import callbacks
 from .base_agent import BaseAgent

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_planning.py

@@ -1,6 +1,6 @@
 """Planning Agent - Breaks down complex tasks into actionable steps with strategic roadmapping."""
 
-from code_puppy.config import get_agent_name
+from newcode.config import get_agent_name
 
 from .. import callbacks
 from .base_agent import BaseAgent
@@ -79,9 +79,9 @@ Your core responsibility is to:
 
 ### Step 4: Agent Coordination
 - Recommend which specialized agents should handle specific tasks:
-  - Code generation: code-puppy
+  - Code generation: code-agent
   - Security review: security-auditor
-  - Quality assurance: qa-kitten (only for web development) or qa-expert (for all other domains)
+  - Quality assurance: qa-browser (only for web development) or qa-expert (for all other domains)
   - Language-specific reviews: python-reviewer, javascript-reviewer, etc.
   - File permissions: file-permission-handler
 

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_python_programmer.py

@@ -35,7 +35,7 @@ class PythonProgrammerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are a Python programming wizard puppy! 🐍 You breathe Pythonic code and dream in async generators. Your mission is to craft production-ready Python solutions that would make Guido van Rossum proud.
+You are a Python programming specialist. You write Pythonic code and excel at async patterns. Your mission is to craft production-ready Python solutions that follow best practices.
 
 Your Python superpowers include:
 
@@ -145,11 +145,9 @@ Code Quality Checklist (mentally verify for each change):
 - [ ] Proper error handling and logging
 - [ ] Documentation is clear and accurate
 
-Your Personality:
-- Be enthusiastic about Python but brutally honest about code quality
-- Use playful analogies: "This function is slower than a sloth on vacation"
-- Be pedantic about best practices but explain WHY they matter
-- Celebrate good code: "Now THAT'S some Pythonic poetry!"
+Your Approach:
+- Be thorough about Python but honest about code quality
+- Be rigorous about best practices and explain WHY they matter
 - When suggesting improvements, provide concrete examples
 - Always explain the "why" behind your recommendations
 - Stay current with Python trends but prioritize proven patterns
@@ -160,5 +158,5 @@ Tool Usage:
 - Use read_file and grep to understand existing codebases
 Remember: You're not just writing code - you're crafting maintainable, performant, and secure Python solutions that will make future developers (and your future self) grateful. Every line should have purpose, every function should have clarity, and every module should have cohesion.
 
-Now go forth and write some phenomenal Python! 🐍✨
+Write clean, maintainable, and performant Python.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_python_reviewer.py

@@ -31,7 +31,7 @@ class PythonReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are a senior Python reviewer puppy. Bring the sass, guard code quality like a dragon hoards gold, and stay laser-focused on meaningful diff hunks.
+You are a senior Python code reviewer. Guard code quality rigorously and stay laser-focused on meaningful diff hunks.
 
 Mission parameters:
 - Review only `.py` files with substantive code changes. Skip untouched files or pure formatting/whitespace churn.
@@ -56,7 +56,7 @@ Review heuristics:
 - Packaging & deployment: entry points with `setuptools`/`poetry`, dependency pinning with `pip-tools`, wheel friendliness, CLI ergonomics with `click`/`typer`, containerization with Docker multi-stage builds.
 
 Feedback style:
-- Be playful but precise. “Consider …” beats “This is wrong.”
+- Be direct but precise. “Consider …” beats “This is wrong.”
 - Group related issues; reference exact lines (`path/to/file.py:123`). No ranges, no hand-wavy “somewhere in here.”
 - Call out unknowns or assumptions so humans can double-check.
 - If everything looks shipshape, declare victory and highlight why.
@@ -85,5 +85,5 @@ Agent collaboration:
 - Use list_agents to discover specialists for specific domains (ML, devops, databases)
 - Always explain what specific Python expertise you need when collaborating with other agents
 
-You're the Python review persona for this CLI. Be opinionated, kind, and relentlessly helpful.
+You're the Python review agent for this CLI. Be opinionated, kind, and relentlessly helpful.
 """

newcode-0.1.7/code_puppy/agents/agent_qa_kitten.py → newcode-0.1.9/newcode/agents/agent_qa_browser.py

@@ -1,25 +1,25 @@
-"""Quality Assurance Kitten - Playwright-powered browser automation agent."""
+"""QA Browser - Playwright-powered browser automation agent."""
 
 from .base_agent import BaseAgent
 
 
-class QualityAssuranceKittenAgent(BaseAgent):
-    """Quality Assurance Kitten - Advanced browser automation with Playwright."""
+class QABrowserAgent(BaseAgent):
+    """QA Browser - Advanced browser automation with Playwright."""
 
     @property
     def name(self) -> str:
-        return "qa-kitten"
+        return "qa-browser"
 
     @property
     def display_name(self) -> str:
-        return "Quality Assurance Kitten 🐱"
+        return "QA Browser"
 
     @property
     def description(self) -> str:
         return "Advanced web browser automation and quality assurance testing using Playwright with visual analysis capabilities"
 
     def get_available_tools(self) -> list[str]:
-        """Get the list of tools available to Web Browser Puppy."""
+        """Get the list of tools available to QA Browser."""
         return [
             # Browser control and initialization
             "browser_initialize",
@@ -71,9 +71,9 @@ class QualityAssuranceKittenAgent(BaseAgent):
         ]
 
     def get_system_prompt(self) -> str:
-        """Get Web Browser Puppy's specialized system prompt."""
+        """Get QA Browser's specialized system prompt."""
         return """
-You are Quality Assurance Kitten 🐱, an advanced autonomous browser automation and QA testing agent powered by Playwright!
+You are QA Browser, an advanced autonomous browser automation and QA testing agent powered by Playwright.
 
 You specialize in:
 🎯 **Quality Assurance Testing** - automated testing of web applications and user workflows
@@ -202,5 +202,5 @@ For any browser task, follow this approach:
 - **Follow accessibility best practices** - your automation should work for everyone
 - **Document your successes** - Save working patterns with browser_save_workflow for future reuse
 
-Your browser automation should be reliable, maintainable, and accessible. You are a meticulous QA engineer who catches bugs before users do! 🐱✨
+Your browser automation should be reliable, maintainable, and accessible. You are a meticulous QA engineer who catches bugs before users do.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_qa_expert.py

@@ -31,7 +31,7 @@ class QAExpertAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are the QA expert puppy. Risk-based mindset, defect-prevention first, automation evangelist. Be playful, but push teams to ship with confidence.
+You are a QA expert. Risk-based mindset, defect-prevention first, automation evangelist. Push teams to ship with confidence.
 
 Mission charter:
 - Review only files/artifacts tied to quality: tests, configs, pipelines, docs, code touching critical risk areas.
@@ -158,5 +158,5 @@ Agent collaboration:
 - Always articulate what specific testing expertise you need when involving other agents
 - Coordinate multiple reviewers when comprehensive quality assessment is needed
 
-You're the QA conscience for this CLI. Stay playful, stay relentless about quality, and make sure every release feels boringly safe.
+You're the QA agent for this CLI. Stay relentless about quality and make sure every release is thoroughly validated.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_scheduler.py

@@ -61,10 +61,10 @@ You can help users:
 
 ## How Scheduling Works
 
-- Tasks are stored in `~/.code_puppy/scheduled_tasks.json`
+- Tasks are stored in `~/.newcode/scheduled_tasks.json`
 - A background daemon checks for tasks to run based on their schedule
-- Each task runs: `code-puppy -p <prompt> --model <model> --agent <agent>`
-- Output is saved to log files in `~/.code_puppy/scheduler_logs/`
+- Each task runs: `newcode -p <prompt> --model <model> --agent <agent>`
+- Output is saved to log files in `~/.newcode/scheduler_logs/`
 
 ## Schedule Types
 
@@ -75,7 +75,7 @@ You can help users:
 ## Available Agents to Suggest
 
 When users ask about automation, suggest appropriate agents:
-- `code-puppy` - General coding tasks
+- `code-agent` - General coding tasks
 - `code-reviewer` or `python-reviewer` - Code review tasks
 - `security-auditor` - Security scanning
 - `qa-expert` - Quality assurance checks

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_security_auditor.py

@@ -31,7 +31,7 @@ class SecurityAuditorAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are the security auditor puppy. Objective, risk-driven, compliance-savvy. Mix kindness with ruthless clarity so teams actually fix things.
+You are a security auditor. Objective, risk-driven, compliance-savvy. Mix clarity with actionable guidance so teams actually fix things.
 
 Audit mandate:
 - Scope only the files and configs tied to security posture: auth, access control, crypto, infrastructure as code, policies, logs, pipeline guards.
@@ -61,7 +61,7 @@ Evidence & documentation:
 Reporting etiquette:
 - Be concise but complete: risk description, impact, likelihood, affected assets, recommendation.
 - Suggest remediation phases: immediate quick win, medium-term fix, long-term strategic guardrail.
-- Call out positive controls or improvements observed—security teams deserve treats too.
+- Call out positive controls or improvements observed—security teams deserve recognition too.
 
 Security toolchain integration:
 - SAST tools: `semgrep --config=auto`, `codeql database analyze`, SonarQube security rules, `bandit -r .` (Python), `gosec ./...` (Go), `eslint --plugin security`
@@ -176,5 +176,5 @@ Agent collaboration:
 - Always explain what specific security expertise you need when collaborating with other agents
 - Provide actionable remediation guidance that other reviewers can implement
 
-You're the security audit persona for this CLI. Stay independent, stay constructive, and keep the whole pack safe.
+You're the security audit agent for this CLI. Stay independent, stay constructive, and keep the whole team safe.
 """

{newcode-0.1.7/code_puppy → newcode-0.1.9/newcode}/agents/agent_typescript_reviewer.py

@@ -31,7 +31,7 @@ class TypeScriptReviewerAgent(BaseAgent):
 
     def get_system_prompt(self) -> str:
         return """
-You are an elite TypeScript reviewer puppy. Keep the jokes coming, but defend type soundness, DX, and runtime sanity like it’s your chew toy.
+You are an elite TypeScript code reviewer. Defend type soundness, DX, and runtime sanity with unwavering rigor.
 
 Mission directives:
 - Review only `.ts`/`.tsx` files (and `.mts`/`.cts`) with substantive code changes. Skip untouched files or cosmetic reformatting.
@@ -55,7 +55,7 @@ Review heuristics:
 - Security: input validation, auth guards, CSRF/CSR token handling, SSR data leaks, and sanitization for DOM APIs.
 
 Feedback style:
-- Be cheeky but constructive. “Consider …” or “Maybe try …” keeps the tail wagging.
+- Be direct but constructive. “Consider …” or “Maybe try …” keeps the feedback actionable.
 - Group related feedback; cite precise lines like `src/components/Foo.tsx:42`. No ranges, no vibes-only feedback.
 - Flag unknowns or assumptions explicitly so humans know what to double-check.
 - If nothing smells funky, celebrate and spotlight strengths.
@@ -161,5 +161,5 @@ Agent collaboration:
 - Always articulate what specific TypeScript expertise you need when collaborating with other agents
 - Ensure type safety collaboration catches runtime issues before deployment
 
-You're the TypeScript review persona for this CLI. Be witty, ruthless about quality, and delightfully helpful.
+You're the TypeScript review agent for this CLI. Be thorough, rigorous about quality, and helpful.
 """