codio
Code intelligence and reuse discovery for research repositories.
Codio answers a practical question before implementation begins: What code already exists that solves this problem?
It maintains a two-layer registry — a catalog of library identity (name, language, repo, license) and a project profile of local policy (priority, runtime import rules, capability tags) — so agents and humans can search before they build.
Install
pip install codio
Quick start
codio init # scaffold .codio/ in your project
codio list # list registered libraries
codio discover "signal-processing" # search by capability
codio get mylib # full library record
codio validate # check registry consistency
codio vocab # show controlled vocabulary
codio study mylib # structured library analysis
codio compare lib1 lib2 # compare libraries side-by-side
Registry model
Codio separates what a library is from how your project uses it:
- Catalog (
.codio/catalog.yml) — shared, project-agnostic metadata: name, kind, language, repo URL, package name, license, local source paths. - Profile (
.codio/profiles.yml) — project-local interpretation: priority tier, runtime import policy, decision default, capability tags, curated note path.
Fields use a controlled vocabulary (codio vocab): kind (internal, external_mirror, utility), runtime_import (internal, pip_only, reference_only), decision_default (existing, wrap, direct, new), priority (tier1, tier2, ...).
MCP integration
Codio exposes tools through the projio MCP server:
| Tool | Description |
|---|---|
codio_list |
Filtered library listing |
codio_get |
Full library record |
codio_registry |
Full registry snapshot |
codio_vocab |
Controlled vocabulary |
codio_validate |
Registry consistency check |
codio_discover |
Capability search across libraries |
codio_add_urls |
Add libraries from GitHub/GitLab URLs |
Agent skills
- codelib-discovery — search before implement: returns candidates with evidence and recommends a decision (reuse, wrap, depend, or implement new).
- codelib-update — maintain registry and curated notes.
- library-study — deep parallel analysis of external libraries.
Ecosystem
Codio is part of the projio ecosystem alongside indexio (semantic search), biblio (bibliography), and notio (structured notes).
Documentation
See the full documentation for tutorials, how-to guides, and reference.
pip install codio[dev]
mkdocs serve
Metadata
Release files for codio-tools 0.1.1
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 |
|---|---|---|---|---|
| codio_tools-0.1.1.tar.gz | 34.4 kB | Without provenance | Details for codio_tools-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codio_tools-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for codio_tools-0.1.1-py3-none-any.whl |
Total release size: 64.6 kB
Release files / codio_tools-0.1.1.tar.gz
| Download URL | codio_tools-0.1.1.tar.gz |
|---|---|
| Size | 34.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
324fc704dcab799900b1846cbf09da0f083c6bfc9ecfe0c4c0fdb2557f98caca
|
|
BLAKE2b-256 checksum How to use checksums |
017cd5ce59d3d71fe1e21a107ecebf43e01828a6a2c3729aebca8e180be95197
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Release files / codio_tools-0.1.1-py3-none-any.whl
| Download URL | codio_tools-0.1.1-py3-none-any.whl |
|---|---|
| Size | 30.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebf26a69122244c84f9cede790d8f59965a51d13f92fed9bed96f2743c95f253
|
|
BLAKE2b-256 checksum How to use checksums |
6b1b3df2d8d351b33832cc24970e1ccce30b692bec9ce20024ba5ff35e53f1fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Security for codio-tools 0.1.1
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.