All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

CoderLM API Reference: REPL Operations to HTTP Endpoints Mapping

By

jared_stewart

3mo ago· 9 min readenCode

Summary

This document provides a technical mapping between REPL operations and API endpoints for CoderLM, a tree-sitter-powered code indexing server. It serves as a reference guide for building agent skills that interact with the server's HTTP API. The content details session management requirements, authentication headers, and specific endpoint mappings for code exploration operations like symbol lookup, implementation finding, caller identification, test discovery, and grep searches across multi-language projects.

Key quotes

· 4 pulled
Every request (except health, session creation, and admin endpoints) must include the X-Session-Id header. The session ties the request to a specific project.
Tree-sitter-powered code indexing server that gives LLM agents precise, on-demand access to symbols, implementations, callers, tests, and grep across multi-language projects - so they explore codeb...
This document maps each REPL operation from the CoderLM design (see PURPOSE.md) to its corresponding API endpoint. Use this as the reference when building the agent skill that wraps these HTTP calls.
All endpoints are prefixed with http://<host>:<port>/api/v1. Examples assume localhost:3000.
Snippet from the RSS feed
Tree-sitter-powered code indexing server that gives LLM agents precise, on-demand access to symbols, implementations, callers, tests, and grep across multi-language projects - so they explore codeb...

You might also wanna read