Overview
Code generation applies language modelling to programming languages. Because code has strict syntax and testable behaviour, output can be verified automatically — which is why this capability moved from novelty to daily tooling faster than most others.
How it works
Models trained on large public code corpora predict the next token given the open file, related files, and the instruction. Modern coding tools add retrieval over the repository, run the test suite, read the failure, and iterate — turning one-shot completion into a short agentic loop.
Supported AI tools
Support level is recorded per tool, so an integration is never shown as a built-in feature.
Use cases
Inline completion
Suggest the next lines as a developer types, using the open file and imports as context.
SoftwareTest generation
Produce unit and edge-case tests for existing functions to raise coverage quickly.
SoftwareFramework migration
Mechanically translate a codebase between versions or languages with human review.
SoftwareCode explanation
Summarise what an unfamiliar module does before changing it.
SoftwareBenefits
- Removes boilerplate and glue-code drudgery.
- Explains unfamiliar code faster than reading it cold.
- Generates test cases and edge cases developers skip.
- Speeds migration work across languages and framework versions.
Limitations
- Confidently produces code that compiles but is subtly wrong.
- May reproduce insecure patterns present in training data.
- Struggles with large, idiosyncratic private codebases without retrieval.
- Licensing of generated snippets is still legally unsettled.
What to look for when choosing a tool
- Repository-wide retrieval, not just open-file context
- Explicit training opt-out in the contract
- IDE and CI integration that fits your workflow
- Self-hosting option if your code cannot leave your network
- Licence-attribution scanning for generated snippets