koneck
v2.25.39
Published
Kinetically Orchestrated Neural Execution Engine for Code
Maintainers
Readme
KONECK
Kinetically Orchestrated Neural Execution Engine for Code
A CLI AI coding agent that works like Claude Code or Codex CLI — drop into a chat, give it a task, and it reads, writes, and runs code autonomously using any LLM provider.
Install
npm install -g koneckThen run koneck — the first-run wizard sets up your API key and provider.
Quick Start
koneck # interactive chat (first run → setup wizard)
koneck "add validation to auth.ts" # one-shot task
koneck --pr "fix the flaky tests" # task + open a PR when doneProviders
| Provider | Env Var | Default Model |
|---|---|---|
| omni (OmniRoute) | OMNI_ROUTE_API_KEY | auto/best-coding |
| openai | OPENAI_API_KEY | gpt-4o |
| anthropic | ANTHROPIC_API_KEY | claude-opus-4-5 |
| google | GOOGLE_API_KEY | gemini-2.0-flash |
| groq | GROQ_API_KEY | llama-3.3-70b-versatile |
| deepseek | DEEPSEEK_API_KEY | deepseek-coder |
| mistral | MISTRAL_API_KEY | mistral-large-latest |
| together | TOGETHER_API_KEY | meta-llama/Llama-3-70b-chat-hf |
| xai | XAI_API_KEY | grok-beta |
| perplexity | PERPLEXITY_API_KEY | llama-3.1-sonar-large-128k-online |
| moonshot | MOONSHOT_API_KEY | moonshot-v1-8k |
| cohere | COHERE_API_KEY | command-r-plus |
| ollama (local) | (none) | llama3.2 |
CLI Reference
Flags
| Flag | Description |
|---|---|
| -p, --provider | LLM provider to use (e.g. openai, anthropic, omni) |
| --base-url | Override the provider base URL |
| -m, --model | Model name to use |
| -t, --max-turns | Maximum agentic turns before stopping |
| -a, --approve | Auto-approve all tool calls |
| -w, --worktree | Run in an isolated git worktree |
| -C, --cwd | Set working directory |
| -v, --verbose | Print full tool call input/output |
| --ci | Non-interactive CI mode |
| --json | Output structured JSON |
| --budget | Token/cost budget limit |
| --pr | Open a pull request when the task completes |
| -V, --version | Print version |
| -h, --help | Show help |
Subcommands
| Subcommand | Description |
|---|---|
| chat | Start an interactive chat session (default) |
| doctor | Check provider connectivity and configuration |
| stats | Show usage statistics |
| watch [pattern] | Watch files matching pattern and re-run on changes |
| setup | Interactive first-run configuration wizard |
| init | Generate a KONECK.md for the current project |
| completion [shell] | Print shell completion script (bash/zsh/fish) |
| --sessions | List recent sessions |
| --resume <id> | Resume a previous session by ID |
Quality and governance
KONECK verifies changed projects after a coding task by running the detected lint
and test commands. In chat, run /quality at any time to repeat that check.
Every top-level tool operation is also appended to .koneck/audit/ as a
structured JSONL event with its timestamp, duration, outcome, and a redacted
action summary. File contents are never stored in the audit trail. Use
/audit or /audit 50 in chat to inspect recent activity.
Repository policy
Run /policy init in chat to create .koneck/policy.json. The policy is
enforced before built-in file and command tools execute. It can protect secret
paths, block dangerous command patterns, require approval for selected tools,
and limit writes to specified paths.
Workspace trust and updates
When KONECK is opened in an interactive folder, it asks whether it may access that workspace for the current session, always, or not at all. Persistent workspace approvals are stored locally in the user's KONECK configuration.
KONECK also checks the npm registry at most once per day and shows an upgrade notice when a newer published version is available. It never installs or publishes updates automatically.
KONECK.md
Place a KONECK.md in your project root to give KONECK project-specific context — architecture notes, conventions, commands to run before editing, files to avoid, and anything else the agent should know up front.
Run koneck init to auto-generate one from your existing codebase, or koneck setup to walk through it interactively.
MCP Servers
KONECK supports Model Context Protocol servers declared in .koneck/mcp.json:
// .koneck/mcp.json
{
"servers": {
"github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"] }
}
}Servers are started automatically when KONECK launches and their tools become available to the agent.
Configuration
Global config lives in ~/.koneckrc:
{ "provider": "anthropic", "model": "claude-opus-4-5", "baseURL": "https://..." }Project-level config can be placed in .koneck/config.json and takes precedence over the global config.
License
MIT
