NewCode
NewCode is an open-source, terminal-first AI coding agent for generating, editing, and reviewing code directly from your CLI.
It is maintained as a fork of code-puppy, with a more professional default UX and workflow-focused agent setup.
Why NewCode
NewCode is designed for practical software workflows in the terminal: inspect files, make edits, run commands, and iterate quickly with AI assistance.
Features
- Multi-provider model support (including OpenAI, Anthropic, Gemini, Cerebras, and compatible OpenAI-style endpoints)
- Terminal-first coding workflow (read/search/edit/delete files and run commands)
- Built-in agent system with a default coding agent and optional specialist workflows
- MCP (Model Context Protocol) integration and server management
- Interactive command-driven UX for model, agent, and settings management
- Session autosave/restore utilities
- Plugin/callback extensibility hooks
Quick start
1) Install
pip install newcode
Or with uv:
uv pip install newcode
2) Launch
newcode
Short alias:
nc
On first run, NewCode starts onboarding to help configure API keys and defaults.
3) First useful commands
/config # Show current configuration
/model # Select or switch model
/agent # Select or switch agent
/colors # Customize terminal UI colors
Requirements
- Python
>=3.11,<3.14 - At least one provider/API key for a supported model backend
Configuration
NewCode uses a legacy-compatible config filename: puppy.cfg.
- Default path:
~/.newcode/puppy.cfg - With XDG variables:
$XDG_CONFIG_HOME/newcode/puppy.cfg
Development
git clone https://github.com/janfeddersen-wq/new_code.git
cd new_code
uv pip install -e ".[dev]"
Testing
Run the test suite:
uv run pytest tests/ -v
Run linting and formatting checks:
ruff check .
ruff format --check .
Contributing
Contributions are welcome.
- Open an issue to discuss bugs, ideas, or improvements.
- Submit a pull request with a clear scope and rationale.
- Keep changes focused and include tests when applicable.
License
MIT — see LICENSE.
Metadata
Release files for newcode 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| newcode-0.3.2.tar.gz | 624.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| newcode-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / newcode-0.3.2.tar.gz
| Download URL | newcode-0.3.2.tar.gz |
|---|---|
| Size | 624.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d49a73f1496d493aab285f510a9e16807ffa1e38d2ce9a41a02d5e66ede1d6b
|
|
BLAKE2b-256 checksum How to use checksums |
d80defaccb69efd59724009a6c8164eb74aa11b9c245e8279a0a831ae4a4c606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 23, 2026.
Transparency logRelease files / newcode-0.3.2-py3-none-any.whl
| Download URL | newcode-0.3.2-py3-none-any.whl |
|---|---|
| Size | 776.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c86392c737bf321039bc9bbc3310bac1851a694b62941dd032f1d2a36c7998ae
|
|
BLAKE2b-256 checksum How to use checksums |
c6b44d8aee8efb14e7779a9481d691d976ddd3958a69751c5690d4bf30b2be47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 23, 2026.
Transparency log