HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
smol-ai
developer
Python2023–2024
smol-ai / developer

developer

the first library to let you embed a developer agent in your own app!

10Distinct people
11Mentions
0Explicit recommenders
12.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

the first library to let you embed a developer agent in your own app!

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month11 dated mentions

Observed mentions: 2023-05-14 23:36:37 UTC to 2024-10-04 00:57:36 UTC.

012342023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsMay 20232023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 20242024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC321
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC101
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC422
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC110
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC000
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC101
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC000
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC000
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC000
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC101

What Hacker News says

4 sources
bko·Aug 15, 2023Submission

Show HN: A CLI tool to have LLMs edit and add code to an existing code base

I've been experimenting with GPT to try to write code in an existing code base. This consists mainly of copy and pasting existing code snippets and getting edits or adding new functions. Or using tools like smol-dev [0] to generate entire projects me for j-dev originally started as a refactor of smol-dev but I quickly realized it was unrealistic to nuke your entire project and rebuild from scratch. Plus it was overly expensive in terms of tokens used. j-dev is meant to be used in existing projects and allows the LLM have discretion over what it need to know about your codebase, while giving the user full control. j-dev also handles invalid responses, and updates your code with permission, all while providing full transparency and a relatively simple implementation. From experience using it, it's somewhat useful although still often has a
Read the rest
shallow understanding of the code base despite being able to request more. But hopefully this gets better as LLMs improve or I get better at prompt engineering. [0] https://github.com/smol-ai/developer
2 points · Open discussion
jessemhan·Aug 9, 2023Submission

Show HN: Rift – Open-source AI-native language server for your personal AI SWE

Howdy y'all, I'm Jesse and I'm pleased to share Rift (https://www.github.com/morph-labs/rift), an open-source AI-native language server for the IDEs of the future. Software will soon be written mostly by AI SWEs working alongside humans. Codebases and the development environments around them will soon become living artifacts that can anticipate, maintain context on, and execute your every intention. Software development is rapidly evolving and key infrastructure like language servers must evolve with it to support a new generation of developer tools. As part of Rift, we're releasing an open-source VSCode extension which shows what is possible today with a language server that can mediate between LLMs and IDEs, and which takes a first step towards a future where you can build and iterate on entire projects with only natural language gestur
Read the rest
es. Today, with Rift, you can do all of the following without ever leaving VSCode or copy-pasting from a browser chat window: - Generate an entire workspace, or a module based on other parts of your codebase - Conversationally iterate on code edits over selected regions which are streamed directly into your editor window - Request, review, and iterate on codebase-wide, multi-file edits Everything runs as an agent through Rift's Agents API. You can define your own agents that can interact directly with your IDE and codebase through the language server, and can run arbitrary Python code that can do things like: - provide a conversational UI over the git CLI (e.g. 'suggest fixes for these merge conflicts, then rebase over myBranch') - real-time automatic docstring generation triggered by saving a file or making a git commit - run tools like typecheckers and static analyzers in the background and implement fixes based on their output - automated code review in your IDE with context from GitHub We're proud to integrate with open-source projects like Smol Developer (https://www.github.com/smol-ai/developer), GPT Engineer (https://www.github.com/antonosika/gpt-engineer), and Aider (https://www.github.com/paul-gauthier/aider). Language servers are ubiquitous and see every action you take in an IDE. Rift will soon support recording training data from your interactions so that you can work with a team of truly personalized AI software engineers. At Morph Labs (https://morph.so), we believe that the future of software development should be transparent, open-source, and defined collectively by the developer community. The Rift language server and extension will continue to be open-source, extensible, and privacy/security aware with opt-in telemetry and first-class support for custom endpoints and on-device models — no closed source language server binaries, no API calls to mysterious proxy servers. We would love for you to try out Rift and give us feedback! Please let us know what you think in the comments.
17 points · Open discussion
1) Show HN: Bloop – Answer questions about your code with an LLM agent (github.com/bloopai) https://news.ycombinator.com/item?id=36260961 2) https://github.com/paul-gauthier/aider 3) Show HN: GPT Repo Loader – load entire code repos into GPT prompts (github.com/mpoon) https://news.ycombinator.com/item?id=35191303 4) https://github.com/smol-ai/developer 5) codium 6) copilot 7) using gpt in the playground / chatgpt 8) jam.dev/jamgpt 9) magic.dev 10) https://github.com/kristoferlund/duet-gpt Which ones am I missing?
In Ask HN: Which GPT-powered coding assistants exist?
I had a similar thought, but would I would like to maintain control what the LLM has access to. It would be difficult to prevent things you might temporarily have hardcoded or generally do not want to expose. I started working on something for this purpose called j-dev [0]. It started as a fork off smol-dev [1] which basically gets GPT to write your entire project from scratch. And then you would have to iterate the prompt to nuke everything and re-write everything, filling in increasingly complicated statements like "oh except in this function make sure you return a promise" j-dev is a CLI where it gives a prompt similar to the one in the parent article [2]. You start with a prompt and the CLI fills in the directory contents (excluding gitignore). Then it requests access to the files it thinks it wants. And then it can edit, delete or ad
Read the rest
d files or ask for followup based on your response. It does stuff like make sure the file exists, show you a git diff of changes, respond if the LLM is not following the system prompt, etc. It also addresses the problem that a lot of these tools eat up way too many tokens so a single prompt to something like smol-dev would eat up a few dollars on every iterations. It's still very much a work in progress and i'll prob do a show hn next week but I would love some feedback [0] https://github.com/breeko/j-dev [1] https://github.com/smol-ai/developer [2] https://github.com/breeko/j-dev/blob/master/src/prompts/syst...
In Add an AI Code Copilot to your product using GPT-4

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.