Datalyn Code
A coding agent for your terminal (and for VS Code, with the Datalyn Code extension). It reads, edits and tests your code; every file change and every command is shown to you before it happens.
Install
# 1. uv (https://docs.astral.sh/uv/)
curl -LsSf https://astral.sh/uv/install.sh | sh
# 2. the engine: `dlc` and `datalyn-code` on your PATH
uv tool install datalyn-code
# 3. a model: a Gemini key (free tier: https://aistudio.google.com/apikey) ...
mkdir -p ~/.datalyn && echo 'GEMINI_API_KEY=<your key>' >> ~/.datalyn/.env
# ... or Ollama on your machine (no key), or OLLAMA_API_KEY for Ollama Cloud
Then, in a project folder: dlc. Check the installation with dlc doctor; dlc --version gives
the version. Update with uv tool upgrade datalyn-code.
Optional Opik tracing: uv tool install "datalyn-code[opik]".
Use
dlc: the terminal interface. Type a request; Enter sends, Esc stops,/helplists the commands.dlc run "fix the failing test": one task without questions, in the Docker sandbox, with a JSON result for scripts and CI (--output json).dlc serve: the JSON-RPC server the VS Code extension talks to.
Models
Gemini (default gemini-2.5-flash, key GEMINI_API_KEY), Ollama on your machine (free; your code
stays on it), Ollama Cloud (OLLAMA_API_KEY), OpenRouter (OPENROUTER_API_KEY), and any
OpenAI-compatible API you add. A model is provider:name: dlc --model ollama:gemma4:12b; /model
lists them and switches between two turns.
Safety
- Permission modes: Default (asks before each file change and command), Edit, Plan (read-only), Bypass (no question, confirmed and shown).
- Keys stay in
~/.datalyn/.envor the project's.env; they are never shown nor logged. - With a cloud model (Ollama Cloud, OpenRouter, Gemini), your code is sent to that provider.
- No telemetry: Datalyn Code sends nothing anywhere except to the model provider you choose (and to Opik, only if you configure it).
License
Proprietary. Copyright © 2026 DATALYN. All rights reserved. See the LICENSE file. Website: https://datalyn.fr
Datalyn Code en français
Un agent de codage pour votre terminal (et pour VS Code, avec l'extension Datalyn Code). Il lit, modifie et teste votre code ; chaque modification de fichier et chaque commande vous est montrée avant d'avoir lieu.
Installation
# 1. uv (https://docs.astral.sh/uv/)
curl -LsSf https://astral.sh/uv/install.sh | sh
# 2. le moteur : `dlc` et `datalyn-code` dans votre PATH
uv tool install datalyn-code
# 3. un modèle : une clé Gemini (offre gratuite : https://aistudio.google.com/apikey) ...
mkdir -p ~/.datalyn && echo 'GEMINI_API_KEY=<votre clé>' >> ~/.datalyn/.env
# ... ou Ollama sur votre machine (sans clé), ou OLLAMA_API_KEY pour Ollama Cloud
Puis, dans un dossier de projet : dlc. dlc doctor vérifie l'installation, dlc --version donne
la version, uv tool upgrade datalyn-code met à jour. Traces Opik en option :
uv tool install "datalyn-code[opik]".
Utilisation
dlc: l'interface en terminal. Entrée envoie, Échap arrête,/helpliste les commandes.dlc run "corrige le test qui échoue": une tâche sans question, dans le bac à sable Docker, avec un résultat JSON pour les scripts et la CI (--output json).dlc serve: le serveur JSON-RPC de l'extension VS Code.
Modèles
Gemini (par défaut gemini-2.5-flash, clé GEMINI_API_KEY), Ollama sur votre machine (gratuit ;
votre code y reste), Ollama Cloud (OLLAMA_API_KEY), OpenRouter (OPENROUTER_API_KEY), et toute API
compatible OpenAI que vous ajoutez. Un modèle s'écrit fournisseur:nom : dlc --model ollama:gemma4:12b ; /model les liste et en change entre deux tours.
Sécurité
- Modes de permission : Par défaut (demande avant chaque modification et commande), Édition, Plan (lecture seule), Bypass (sans question, confirmé et signalé).
- Les clés restent dans
~/.datalyn/.envou le.envdu projet ; jamais affichées ni journalisées. - Avec un modèle cloud (Ollama Cloud, OpenRouter, Gemini), votre code est envoyé à ce fournisseur.
- Aucune télémétrie : Datalyn Code n'envoie rien nulle part, sauf au fournisseur de modèle que vous choisissez (et à Opik, seulement si vous le configurez).
Licence
Propriétaire. Copyright © 2026 DATALYN. Tous droits réservés. Voir le fichier LICENSE. Site : https://datalyn.fr
Metadata
Release files for datalyn-code 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| datalyn_code-1.3.0.tar.gz | 222.0 kB | Without provenance | Details for datalyn_code-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datalyn_code-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for datalyn_code-1.3.0-py3-none-any.whl |
Total release size: 494.3 kB
Release files / datalyn_code-1.3.0.tar.gz
| Download URL | datalyn_code-1.3.0.tar.gz |
|---|---|
| Size | 222.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6dd33997e753c5858e7e4b79b2c08b94d2dc12d9e2b46835cc004cc1aa678852
|
|
BLAKE2b-256 checksum How to use checksums |
84cc0ee2bf17c054b95e936abd1e8b3d85a61f810b86f72a423037c6e2d6bfe5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / datalyn_code-1.3.0-py3-none-any.whl
| Download URL | datalyn_code-1.3.0-py3-none-any.whl |
|---|---|
| Size | 272.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fb45065dbe44e8cd68de93d9beab8b7f9db03d43b4e584c2882dbc795b8bdff
|
|
BLAKE2b-256 checksum How to use checksums |
d0d7f5da9035a53337d7de947208a06b40b32286d8335d4f99260615013b981d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for datalyn-code 1.3.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.