Been experimenting with an autonomous AI agent for @baysemarkets , a prediction market.
Ran it this morning it placed 2 trades on its own, hit +63.52% P&L, then closed out with a โฆ1,045 balance.
One thing I look out for when trying out opensource tools is a relatively simple setup.
In the same regard, for Kontext, no 17-step installation guide. No dependency wars.
Just:
clone
configure your .env
Pull image from docker hub/build
docker compose up
Hosting this should take minutes.
I've been talking about this for a while. Here's the whole story. ๐งต
1/ It started with a personal problem.
Quite a number of meetings. Notes scattered everywhere. Tried to pay for a proper meeting assistant.
The price? Nope.Too high for the value I'll get.
2/ So I built my own.
As I kept improving it, something hit me
A lot of people probably feel exactly how I felt. But not everyone has the time or the skill to build it themselves.
So I decided to open source it: https://t.co/NS1CxWCFY9
Used it in a real meeting this evening.
@AltSchoolAfrica onboarding session.
Here's what happened
transcription, live, as people spoke
periodic summary, auto-generated mid-meeting
final structured summary when the meeting ended
Then I just told it to send meeting summary to a mail
landed in my inbox. Done.
No copy-pasting. No manual notes. No third-party storing any of it.
All of this ran on my PC locally.
Who actually owns your meeting transcripts?
Otter ai? Fireflies?
Every word spoken in your meetings strategy sessions, client calls, internal standups is sitting on someone else's server.
What happens to it? You'll never know
An open-source alt is otw.