Generate implementation code from a specification.

Use this tool when you need the local model to write a function, class, module, API endpoint, CRUD logic, glue code, or any other implementation artefact. Provide as much context and constraints as possible for the best results.

IMPORTANT: Always review the returned code before accepting it.

Generate test code for a given implementation.

Produces a complete, runnable test file that covers happy paths and edge cases. Specify the testing framework and any particular scenarios you want covered.

IMPORTANT: Always review the returned tests before accepting them.

Apply a specific refactoring to existing code.

The local model will apply the requested transformation while preserving external API and behavior. Useful for mechanical refactors like renaming, extracting methods, converting patterns, etc.

IMPORTANT: Always review the returned code before accepting it.

Fix bugs in code based on errors or review feedback.

Provide the broken code along with compiler/runtime errors and/or reviewer comments. The local model will return a corrected version that addresses all reported issues.

IMPORTANT: Always review the returned fix before accepting it.

Generate documentation for existing code.

Produces documentation in the requested style — inline docstrings, README content, or structured API reference.

IMPORTANT: Always review the returned documentation for accuracy.

Check if the local llama.cpp server is reachable and loaded.

Returns availability status and model metadata. Call this before starting a batch of implementation tasks, or when a previous tool call failed with a connection error, to decide whether to retry or fall back to direct cloud-model implementation.