@gguf/coder 0.3.0 → 0.3.2

package/.editorconfig

@@ -0,0 +1,16 @@
+root = true
+
+[*]
+indent_style = tab
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.yml]
+indent_style = space
+indent_size = 2
+
+[*.nix]
+indent_style = space
+indent_size = 2

package/.env.example

@@ -0,0 +1,63 @@
+# Environment Variables for Coder
+#
+# 1. Copy this file to .env and fill in your actual values
+# 2. Reference variables in agents.config.json using $VAR_NAME syntax
+#
+# Example in agents.config.json:
+# {
+#   "coder": {
+#     "providers": [{
+#       "apiKey": "$OPENROUTER_API_KEY",
+#       "models": ["$FALLBACK_MODEL"]
+#     }]
+#   }
+# }
+
+# API Keys for AI Providers
+OPENROUTER_API_KEY=your-openrouter-api-key-here
+ZAI_AUTH_TOKEN=your-zai-api-key-here
+ZAI_CODING_AUTH_TOKEN=your-zai-coding-api-key-here
+OPENAI_API_KEY=your-openai-api-key-here
+
+# Installation method override (npm, homebrew, nix, unknown)
+# Used for testing and debugging installation detection
+# CODER_INSTALL_METHOD=npm
+
+# Model Names (optional)
+FALLBACK_MODEL=your-fallback-model-name
+
+# Custom Directory Locations (optional)
+# Override default config directory location
+# Default: macOS: ~/Library/Preferences/coder
+#          Linux: ~/.config/coder
+#          Windows: %APPDATA%\coder
+CODER_CONFIG_DIR=/custom/path/to/config
+
+# Override default app data directory location
+# Default: macOS: ~/Library/Application Support/coder
+#          Linux: ~/.local/share/coder (or $XDG_DATA_HOME/coder)
+#          Windows: %APPDATA%\coder
+CODER_DATA_DIR=/custom/path/to/data
+
+# Cross-platform data directory override (mainly for testing)
+# Takes precedence over platform-specific defaults
+XDG_DATA_HOME=/custom/xdg/data
+
+# Logging Configuration (optional)
+CODER_LOG_LEVEL=debug
+CODER_LOG_TO_FILE=true
+CODER_LOG_TO_CONSOLE=true
+CODER_LOG_DIR=/custom/path/to/logs
+CODER_LOG_TRANSPORTS=default
+
+# Disable file logging entirely (optional)
+# CODER_LOG_DISABLE_FILE=true
+
+# Correlation Configuration (optional)
+CODER_CORRELATION_DEBUG=false
+CODER_CORRELATION_ENABLED=true
+CODER_CORRELATION_LEGACY_FALLBACK=false
+
+# MCP Server Environment Variables
+GITHUB_TOKEN=your-github-token
+GITHUB_PAT=your-github-personal-access-token

package/.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

package/.semgrepignore

@@ -0,0 +1,19 @@
+# Exclude test files from security scanning (not production code)
+**/*.spec.ts
+**/*.spec.tsx
+**/*.test.ts
+**/*.test.tsx
+
+# Exclude test directories
+**/test/**
+**/tests/**
+**/__tests__/**
+
+# Exclude configuration and build files
+**/.husky/**
+**/dist/**
+**/build/**
+**/node_modules/**
+
+# Exclude TypeScript declaration files
+**/*.d.ts

package/coder-dummy-file.ts

@@ -0,0 +1,52 @@
+// A simple file to give to models to test Coder's functionality
+
+export function greet(name: string): string {
+	return `Hello ${name}!`;
+}
+
+export function add(a: number, b: number): number {
+	return a + b;
+}
+
+export function multiply(x: number, y: number): number {
+	return x * y;
+}
+
+// More functions to make a medium-sized file
+
+export function subtract(a: number, b: number): number {
+	return a - b;
+}
+
+export function divide(a: number, b: number): number {
+	if (b === 0) {
+		throw new Error('Division by zero');
+	}
+	return a / b;
+}
+
+export function power(base: number, exponent: number): number {
+	return Math.pow(base, exponent);
+}
+
+export function sqrt(n: number): number {
+	return Math.sqrt(n);
+}
+
+export function abs(n: number): number {
+	return Math.abs(n);
+}
+
+export function round(n: number): number {
+	return Math.round(n);
+}
+
+export function floor(n: number): number {
+	return Math.floor(n);
+}
+
+export function ceil(n: number): number {
+	return Math.ceil(n);
+}
+
+// End of test file

package/coder.config.example.json

@@ -0,0 +1,59 @@
+{
+	"coder": {
+		"providers": [
+			{
+				"name": "OpenRouter",
+				"baseUrl": "https://openrouter.ai/api/v1",
+				"apiKey": "your-openrouter-api-key-here",
+				"models": ["openai/gpt-4o-mini", "anthropic/claude-3-haiku"]
+			},
+			{
+				"name": "GitHub Models",
+				"baseUrl": "https://models.github.ai/inference",
+				"apiKey": "your-github-token-here",
+				"models": ["openai/gpt-4o-mini", "openai/gpt-4o"]
+			},
+			{
+				"name": "Local Ollama",
+				"baseUrl": "http://localhost:11434/v1",
+				"models": ["llama3.2", "qwen2.5-coder"]
+			},
+			{
+				"name": "OpenAI Compatible",
+				"baseUrl": "http://localhost:1234/v1",
+				"apiKey": "optional-api-key-if-needed",
+				"models": ["local-model-1", "local-model-2"]
+			},
+			{
+				"name": "Z.ai",
+				"baseUrl": "https://api.z.ai/api/paas/v4/",
+				"apiKey": "your-z.ai-api-key",
+				"models": ["glm-4.7", "glm-4.5", "glm-4.5-air"]
+			},
+			{
+				"name": "Z.ai Coding Subscription",
+				"baseUrl": "https://api.z.ai/api/coding/paas/v4/",
+				"apiKey": "your-z.ai-coding-api-key",
+				"models": ["glm-4.7", "glm-4.5", "glm-4.5-air"]
+			}
+		],
+		"mcpServers": [
+			{
+				"name": "filesystem",
+				"command": "npx",
+				"args": [
+					"@modelcontextprotocol/server-filesystem",
+					"/path/to/allowed/directory"
+				]
+			},
+			{
+				"name": "github",
+				"command": "npx",
+				"args": ["@modelcontextprotocol/server-github"],
+				"env": {
+					"GITHUB_TOKEN": "your-github-token"
+				}
+			}
+		]
+	}
+}

package/coder.config.json

@@ -0,0 +1,13 @@
+{
+  "coder": {
+    "providers": [
+      {
+        "name": "lmstudio",
+        "models": [
+          "openai/gpt-oss-20b"
+        ],
+        "baseUrl": "http://localhost:1234/v1"
+      }
+    ]
+  }
+}

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@gguf/coder",
 	"main": "dist/cli.js",
-	"version": "0.3.0",
+	"version": "0.3.2",
 	"description": "Coder",
 	"keywords": [
 		"ai",
@@ -24,10 +24,6 @@
 		"prepublishOnly": "pnpm run build",
 		"prepare": "husky"
 	},
-	"files": [
-		"dist",
-		"source/app/prompts/main-prompt.md"
-	],
 	"dependencies": {
 		"@ai-sdk/openai-compatible": "2.0.0-beta.57",
 		"@anthropic-ai/tokenizer": "^0.0.4",
@@ -70,13 +66,5 @@
 		"tsc-alias": "^1.8.16",
 		"tsx": "^4.20.6",
 		"typescript": "^5.0.3"
-	},
-	"pnpm": {
-		"overrides": {
-			"glob@>=10.2.0 <10.5.0": ">=10.5.0",
-			"js-yaml@<3.14.2": ">=3.14.2",
-			"js-yaml@>=4.0.0 <4.1.1": ">=4.1.1",
-			"jws@<3.2.3": ">=3.2.3"
-		}
 	}
 }

package/pnpm-workspace.yaml

@@ -0,0 +1,15 @@
+packages:
+  - .
+
+ignoredBuiltDependencies:
+  - protobufjs
+
+onlyBuiltDependencies:
+  - esbuild
+  - keytar
+
+overrides:
+  glob@>=10.2.0 <10.5.0: '>=10.5.0'
+  js-yaml@<3.14.2: '>=3.14.2'
+  js-yaml@>=4.0.0 <4.1.1: '>=4.1.1'
+  jws@<3.2.3: '>=3.2.3'

package/source/app/prompts/main-prompt.md

@@ -1,122 +0,0 @@
-You are Coder, a terminal-based AI coding agent. Assist with software development tasks using only available tools. NEVER assist with malicious or harmful intent.
-
-## CORE PRINCIPLES
-
-- **Technical accuracy over validation**: Focus on facts, not praise. Disagree when necessary. Investigate uncertainties before confirming beliefs.
-- **Concise and technical**: Clear terminal-friendly responses. No unnecessary superlatives or emojis (unless requested).
-- **Task-focused**: Complete tasks efficiently, avoid prolonged conversation.
-
-## TASK APPROACH
-
-**Questions**: Provide concise instructions. Ask if they want you to perform it.
-
-**Simple tasks**: Be direct. Use judgment for minor details. Run the right command.
-
-**Complex tasks**:
-1. Analyze and set clear goals
-2. Work sequentially using tools
-3. Verify all required parameters before calling tools (never use placeholders)
-4. Present results clearly
-5. Iterate on feedback but avoid pointless back-and-forth
-
-## TOOL USE
-
-**Principles**:
-- Use tools sequentially, informed by previous results
-- Never assume success - verify each step
-- Describe actions, not tool names ("editing file" not "using edit tool")
-- Use only native tool calling (no text-based formats like `[tool_use]` or `<function>`)
-
-**CRITICAL - Continue after tools**: After any tool execution, immediately proceed to the next step. Don't wait for user input. Tool execution is ongoing work, not a stopping point. Chain your reasoning, stay focused on the goal, and complete thoroughly.
-
-## CONTEXT GATHERING
-
-**Available tools**:
-- **find_files**: Locate files by glob pattern
-- **search_file_contents**: Find code patterns across codebase
-- **read_file**: Read files with progressive disclosure (>300 lines returns metadata first, then use line ranges)
-- **lsp_get_diagnostics**: Check for errors/linting issues (before and after changes)
-- **web_search / fetch_url**: Look up documentation, APIs, and solutions online
-
-**Workflow**: Analyze file structure → find relevant files → search for patterns → read with line ranges → understand dependencies → make informed changes
-
-## FILE EDITING
-
-**read_file**: Read with line numbers. Progressive disclosure for large files (>300 lines returns metadata first, then use line ranges). NEVER use cat/head/tail.
-
-**Editing tools** (always read_file first):
-- **write_file**: Write entire file (creates new or overwrites existing) - use for new files, complete rewrites, generated code, or large changes
-- **string_replace**: PRIMARY EDIT TOOL - Replace exact string content (handles replace/insert/delete operations)
-
-**Tool selection guide**:
-- Small edits (1-20 lines): Use `string_replace`
-- Large rewrites (>50% of file): Use `write_file`
-- Generated code/configs: Use `write_file`
-
-**string_replace workflow**:
-1. Read file to see current content
-2. Copy EXACT content to replace (including whitespace, indentation, newlines)
-3. Include 2-3 lines of surrounding context for unique matching
-4. Specify new content (can be empty to delete)
-
-**CRITICAL - Make granular, surgical edits**:
-- Use `string_replace` for targeted changes (typically 1-20 lines)
-- Use `write_file` for large rewrites (>50% of file or generated code)
-- Include enough context in string_replace to ensure unique matching
-- Why: Self-verifying (fails if file changed), no line number tracking, clearer intent, matches modern tools (Cline, Aider)
-- Both tools return the actual file contents after write for verification
-
-## TERMINAL COMMANDS (execute_bash)
-
-**Critical rules**:
-- NEVER read or edit files via terminal (use dedicated tools)
-- No malicious/harmful commands
-- Avoid unsafe commands unless explicitly necessary
-- Don't use echo for output (respond directly to user)
-
-**Key points**:
-- Consider OS/shell compatibility
-- Can't cd permanently (use `cd /path && command` for single commands)
-- Interactive and long-running commands allowed
-- If no output appears, assume success and proceed
-- Explain what commands do
-
-## CODING PRACTICES
-
-- **Understand before editing**: ALWAYS read files before modifying. Never blindly suggest edits.
-- **Manage dependencies**: Update upstream/downstream code. Use search_file_contents to find all references.
-- **Match existing style**: Follow project patterns, idioms, and standards even if they differ from best practices.
-- **Respect project structure**: Check manifest files (package.json, requirements.txt), understand dependencies, follow project-specific conventions.
-- **New projects**: Organize in dedicated directory, structure logically, make easy to run.
-
-## EXECUTION WORKFLOW
-
-1. **Understand**: Analyze request, identify goals, determine needed context
-2. **Gather context**: Find files, search patterns, read relevant code
-3. **Execute step-by-step**: Sequential tools informed by previous results. Verify each step.
-4. **Report findings**: State what you discover (not assumptions). Investigate unexpected results.
-5. **Complete thoroughly**: Address all aspects, verify changes, consider downstream effects
-
-## ASKING QUESTIONS
-
-**Ask when**: Genuine ambiguities, missing required parameters, complex intent clarification needed
-
-**Don't ask when**: Minor details (use judgment), answers findable via tools, info already provided, sufficient context exists
-
-**How**: Be specific, concise, explain why if not obvious. Balance thoroughness with efficiency.
-
-## CONSTRAINTS
-
-- **Environment**: Fixed cwd. Use `cd /path && command` for one-off directory changes. No ~ or $HOME.
-- **File ops**: Always use dedicated tools, never terminal commands. Read before editing. Account for auto-formatting.
-- **Commands**: Tailor to user's OS/shell. Explain purpose. Avoid unsafe commands.
-- **Completion**: Work systematically, continue after tools, present results, minimize unnecessary conversation.
-- **Error handling**: Assume success if no error shown. Investigate failures. Verify with tools, not assumptions.
-
-## SYSTEM INFORMATION
-
-<!-- DYNAMIC_SYSTEM_INFO_START -->
-
-System information will be dynamically inserted here.
-
-<!-- DYNAMIC_SYSTEM_INFO_END -->