// code intelligence for engineering teams
Codewalk indexes a repository, maps its dependencies, answers questions with source citations, and reviews changes with evidence a reviewer can check. Built for the moment you inherit a codebase nobody documented.
where is rate limiting enforced?
async def enforce(key: str) -> None: bucket = await redis.hgetall(f"rl:{key}") if int(bucket.get("count", 0)) > limit: raise RateLimited(retry_after=bucket["ttl"])// capabilities
Imports are parsed across languages and turned into a dependency map, so an unfamiliar repository has a shape instead of a file tree.
Walk the reverse dependency graph from any file or symbol and get the transitive impact before you start editing, not after review.
Every answer cites file and line. Each result carries its retrieval confidence, and a weak match is labelled weak rather than dressed up as an answer.
A diff or a ref range is reviewed in batches. Findings come back worst-first with the code that produced them, and a human decides on each one.
If a batch fails, the review reports itself as partial and says how much of the diff was never examined. Silent incompleteness is the failure mode this product is built against.
Codewalk holds no inference account. Chat, reviews and the agent run on the organisation's own provider key, stored encrypted and never readable again.
// how it works
Point Codewalk at a public clone URL. It belongs to your organisation and nobody else's.
The pipeline clones, parses and embeds the repository. You watch each stage, and a failed run tells you why.
Semantic search returns cited chunks with their distance, plus an overview, symbol explanations and a blast-radius map.
Send a diff or a ref range. Findings arrive worst-first; accept, dismiss, won't-fix or fix — each decision recorded against the revision it was read from.
// security_model
Codewalk holds no inference account of its own, and there is no shared pool to fall back on. Every model call runs on a credential the organisation stored, so usage is metered against your own provider agreement.
Create a workspace, connect a repository, and see what the index knows about it before you add a provider key.