| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
CWC is a free and privacy-fist toolkit for AI coding with static context.
CWC provides developers with a complete and free toolkit for pair programming with AI that augments, rather than replaces, traditional coding.
CWC operates 100% on your machine—no code, prompts or usage data are collected.
CWC constructs unified prompts with all relevant files and instructions, so the model has everything it needs from the start. Steer it with examples, focus its attention on specific code, and make simple instructions just work!
CWC helps with all common use-cases like multi-file editing, planning, generating code at cursor or commit messages.
Implement new features, fix bugs and refactor code across many files.
Structure of the constructed prompt# Files [SELECTED FILES] # Output formatting Whenever showing a new, updated, renamed, or deleted file, provide a brief explanation, then print the path in a markdown heading (e.g. ### New file: `src/examples/hello.py`, ### Updated file: `src/examples/hello.py`, ### Renamed file: `src/examples/hello.py` (old) `src/welcome.py` (new), ### Deleted file: `src/examples/hello.py`), followed by a markdown code block showing the original and updated code snippets with Git-style merge conflict syntax. Example: [EXAMPLE] --- [PROMPT]
Plan features or get explanations.
Structure of the constructed prompt# Files [SELECTED FILES] --- [PROMPT]
Quality autocomplete with SOTA reasoning models.
Structure of the constructed prompt# Files [SELECTED FILES] - File `[ACTIVE FILE PATH]`: ``` [PREFIX]<missing_text>[PROMPT]</missing_text>[SUFFIX] ``` # Output formatting Your response must begin with a markdown heading identifying the file and the cursor position, followed by a markdown code block containing the replacement text, followed by a brief explanation. The heading must be: "### Code at cursor: `[ACTIVE FILE PATH]` (ROW:COL)". Always refer to the symbol "<missing_text>" as "cursor position" and "replacement" as "completion". Example: [EXAMPLE] --- Find correct replacement text for the <missing_text> symbol.
Generate commit messages based on staged changes and context files.
Structure of the constructed prompt# Files [SELECTED FILES OF ACCEPTED EDITS] # Changes [STAGED CHANGES] # Output formatting [FORMATTING INSTRUCTIONS] # Task Write a brief and precise summary for the changes, limited to a single sentence. Because the summary will be used for a commit message, don't use any markdown formatting and don't include a trailing dot. Use an imperative tone to ensure clarity and focus on the primary change or purpose.
CWC orders context files by modification and selection recency. This, combined with instructions placement at the message's very end effecively utilizes prompt caching across tasks.
Install the browser extension and never copy and paste again (source code).
Supported chatbots:
Important
The Apply response button placed under responses is not a means of automatic output extraction, it's an alias for the original copy to clipboard button. Review the content script to learn about implementation details.
Note
Use forwarding of port 55155 when using remote machine via SSH.
Copyright © 2026 Robert Piosik
E-mail: robertpiosik@gmail.com
Telegram: robertpiosik
| Back | FazBrowse Home | New Git URL |