HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
llimllib
gpt-bash-cli
Shell2024–2024
llimllib / gpt-bash-cli

gpt-bash-cli

A simple bash interface to openai's API that saves requests and responses to a sqlite database

2Distinct people
2Mentions
0Explicit recommenders
29GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simple bash interface to openai's API that saves requests and responses to a sqlite database

GitHub

Where it is used

No documented product use has been verified yet.

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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM 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 hour2 dated mentions

Observed mentions: 2024-08-02 13:02:11 UTC to 2024-08-02 15:00:03 UTC.

012024-08-02 13:00:00 UTC to 2024-08-02 14:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2, 13:002024-08-02 14:00:00 UTC to 2024-08-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 2, 14:002024-08-02 15:00:00 UTC to 2024-08-02 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2, 15:00

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
Aug 2, 13:002024-08-02 13:00:00 UTC2024-08-02 14:00:00 UTC101
Aug 2, 14:002024-08-02 14:00:00 UTC2024-08-02 15:00:00 UTC000
Aug 2, 15:002024-08-02 15:00:00 UTC2024-08-02 16:00:00 UTC101

What Hacker News says

2 sources
>I prefer using system secret stores to environment variables What is the recommended way to store secrets in a Linux dev machine? The requirement is random scripts and programs should be able to load their secrets like API keys at runtime with minimum hassle. And the secrets shouldn't be stored on disk in plain-text. I see you recommended keyring [1]. Is this "the GNU/linux way"? I see another possibility being storing them in an encrypted filesystem (whether FUSE-based or not) [1]: https://github.com/llimllib/gpt-bash-cli/blob/841682affe2d0e...
In Show HN: Ell – A command-line interface for LLMs written in Bash
I wrote a similar tool I'm no longer maintaining: https://github.com/llimllib/gpt-bash-cli/ . Here are my suggestions: - save the conversations in a sqlite db. ~everyone has sqlite available and it allows the user to do things with the data more easily than a text file - use XDG directories instead of suggesting ~/.ellrcd (https://wiki.archlinux.org/title/XDG_Base_Directory) - I prefer using system secret stores to environment variables; I don't want to give every program I run access to my API keys. You can see how I did that in my program
In Show HN: Ell – A command-line interface for LLMs written in Bash

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.