You can now publish message posts!

• Publish messages as public search indexable posts using the /publish [message-url] slash command
• View published posts from the web dashboard

In this update:

• Add /publish [message-url/id] command to the slack bot
• Add publish post API route
• Add API helper and routes for fetching message, channel and workspace details

AI Usage Info

For adding debug logging into the codebase (helped me save a little time and headache so pls)

Next update

Manage posts (re-post, delete, etc.) feature, /my-posts command

GG

Minor update

• The /set-token [token] command now works.

You use /set-token [token]
|
POST /api/bot/set-token
|
Verify token and find the DB user bound with the token
|
Save token + workspace details (team ID, channel ID) in Database bound to user (so that we don’t need to filter through all API keys every request
|
You’re now ready to publish new posts using the /publish command!

Next update:

Improve the landing page, add a real login page and finally setup the /publish command

You can now create API keys to configure the Slack bot

How it will work:

• Create an API key
• Run the /set-token [token] command with the Sloogle bot
• Done! You’re now authenticated to create and publish new message posts.

In this update:

• Create backend endpoints for fetching and creating new API keys
• Setup configure page with an API keys table and create API key modal
• Add a How to configure the Slack bot section with steps to authenticate yourself with the Sloogle bot

Next: Work on the /set-token [token] command on the Slack bot

Initialized Sloogle Web

• Landing Page with integrated login (better-auth email OTP verification)
• Configure supabase + drizzle ORM as Database and ORM
• Configure Web Dashboard (shadcn/ui dashboard template)

Next up: configure backend route that will receive the slack message object and save it on DB (message content, id, timestamps, channel id, community id, etc.)

First time making a Slack Bot (i was a pro discord bot dev back in 2020)

Initialized and setup the slack bot using Node.js and Slack Bolt

Added a Bot stats command that responds with the following:

You can now configure and bring in your own API Keys

Currently only Gemini API Key is supported which uses the gemini-2.5-flash model

Why bring in your own keys?

Well there’s a 20 message per user daily limit when using the server provided model.

But you definitely might want to talk to your GF more than just 20 messages a day right :) So if you bring in your own keys, you can chat without any limits!

You can view usages of your own keys from the Usage page itself (/account/usage)

Are my keys safe?

Your keys are stored in your browser’s localStorage. It’s not sent to our servers at all. (You can verify checking the opensource code anyways!)

ALSO, thanks to some of you guys who tried out the simulator, tried to jailbreak and manipulate the models, it helped me understand the system a little more.
ALSO, the sim is completely SFW - even if you go NSFW.

LYG<3

Your can now view your Girlfriend’s “Memories”.

Memories are basically a collection of details (birthday, job description, reminders, etc.) you mention/share about yourself in chat. It is stored, so that it can be passed as context for your girlfriend. So now she actually remembers the “small details about you”.

Uses a second LLM call which analyzes your messages to check if any important “detail” about you has been sent, so your girlfriend remembers it.
You can always delete the sensitive ones and recommended.

Lot of updates:

• Chat persistence: Your chats with your GF are now permanently stored in cloud, so you can access the chats anytime.

• Chats infinite scroll: To not display all your 100k messages with your GF at once and break stuff, infinite scroll has been added to chat to load old chats on demand

• Add reaction to messages: You can now react to messages from your girlfriend (and there’s a chance she might get pssed off from that and reply about it). Also your girlfriend can react to your messages too now. * You can currently only react to message groups and now individual message bubble, it’ll be fixed in a future update.

• Added no-reply handler: SO BASICALLY you can be left ON-SEEN or ON-DELIVERED by your girlfriend if you misbehave lol

• Some bug fixes: add limit to user message input, GF’s side texts not being stored in DB, etc.

• Some UI/UX optimizations alongside system prompt optimizations for the MODEL. * I really want to optimize the system prompt even further more ’cause currently it uses almost 1k tokens per message which feels quiet unoptimized and over-usage of tokens

Added:

• Account Page: where you can update your OWN profile details like your avatar, name, description, DOB, MBTI, zodiac, etc. which will let your girlfriend know about you and your personality (from your description of you)

• User Welcome Screen and Navigation Tour: For better UX and understandibility, I have added a welcome screen modal with three steps explaining what the app is about and how it works + sidebar tour for explaining what each link does

• Signout button in account page

Next:: Public Use Launch

made the usage page which shows tokens and messages for the past 14 days

also here are some sample girlfriend responses which felt natural to me

chats now work

model: qwen
the model smh replies and added multi message support

updated message input and added attachment input (menu), emoji selector and GIF picker

also implemented auto-height increment for the message input textarea and enter-is-send and shift-enter-is-not-send for the message input

next: send the message and get a response (basic) via VERCEL AI SDK + Gemini Google API

setup and designed the app interface and the chat page with beautiful starter texts to send to your AI girlfriend and get the convo started.

next: design the chat input section along

Added user authentication (login page) using Google OAuth (better-auth + supabase) setup