1b1f957e01
wip
2025-04-18 14:21:23 +01:00
49969b0608
feat(location-agent): using createLocation instead of updateLocation to simplify
2025-04-18 13:26:42 +01:00
9b95ffb59e
feat(contact-agent): using createContact with an ID field to provide updates
2025-04-17 18:57:13 +01:00
c9560f6881
feat(event-agent): update events function
2025-04-17 18:19:54 +01:00
c5535a5b3b
feat(location-agent): seperating the tool to allow for replying
...
This means it makes less mistakes and doesnt get as confused.
2025-04-17 18:09:00 +01:00
5ab0d13b21
fix(location-events): adding location id to the database from agent call
2025-04-17 15:32:50 +01:00
15289e4965
feat(prompts): adding better prompts & restoring tool_stop
...
Mistral's models seem to do something really strange if you allow for
`tool_choice` to be anything but `any`. They start putting the tool call
inside the `content` instead of an actual tool call. This means that I
need this `stop` mechanism using a tool call instead because I cannot
trust the model to do it by itself.
I quite like this model though, it's cheap, it's fast and it's open
source. And all the answers are pretty good!
2025-04-17 15:24:21 +01:00
181da1f09d
feat(orchestrator): removing the end tool call
...
fix
2025-04-17 13:00:39 +01:00
90b90a8185
chore: removing unnecessary logging
2025-04-17 13:00:24 +01:00
fb30eb4ad6
wip(orchestrator): improving orchestrator system prompt and tool description
2025-04-17 12:52:54 +01:00
5454a1cfaf
feat(event-location): communicating using tool calls correctly
2025-04-17 11:15:02 +01:00
3716d22eca
fix(logger): nil pointer error + log debug level clean
2025-04-17 11:07:37 +01:00
6d2f0c6108
refactor(agents): not returning an error on factory method
2025-04-17 11:02:11 +01:00
61c158d5b6
refactor(agents): encapsulating prompt and calls inside factory method
2025-04-17 10:58:19 +01:00
82331c0833
fix: using correct eventAgent instead of orchestrator bug + better logging
2025-04-17 10:48:30 +01:00
e42aa75639
refactor(agents): no need to wrap them in another struct
2025-04-17 10:36:11 +01:00
fa486153b4
feat: event agent calling location agent about location ID
...
This is pretty nice. We can now have agents spawn other agents and
actually get super cool functionality from it.
The pattern might be a little fragile.
2025-04-16 14:43:07 +01:00
aacecfffac
wip(agents): allowing event agent to call location agent
2025-04-15 16:44:00 +01:00
e89a342751
feat: Adding text message to describe an action3
2025-04-15 16:43:27 +01:00
e16b6f4529
fix
2025-04-14 20:08:07 +01:00
6ddae3426d
rollback: not using link functions as they are very problematic
2025-04-14 10:59:08 +01:00
8a57236f04
ffix
2025-04-14 10:40:02 +01:00
b138661991
prompt
2025-04-14 10:38:25 +01:00
51d36bf15b
more prompt
2025-04-14 10:36:21 +01:00
ecc2da5f86
fix more prompt
2025-04-14 10:33:56 +01:00
1f83b721a6
fix: prompts
2025-04-14 10:28:31 +01:00
5ae6a3403f
chore: removing old agent that was messy and too coupled
...
chore
2025-04-13 16:30:20 +01:00
3156cea904
feat(event): seperate event agent
2025-04-13 16:30:20 +01:00
d432d16752
feat(location): agent to create locations
2025-04-13 16:30:20 +01:00
47c871523d
feat(sse): very rough events. Not used in the client yet
...
feat(sse): very rough events. Not used in the client yet
2025-04-13 14:27:59 +01:00
9bb07c1b9b
fix: tests
2025-04-12 14:43:01 +01:00
959b741fcb
refactor(agent): main agent loop extracted away
...
Still not super sure how to represent these agents in code.
It doesn't make the most amount of sense to keep them in structs. A
curried function is more like it, with system prompt and tooling.
Maybe that's what I'll end up doing.
2025-04-12 14:39:16 +01:00
91cc54aaec
fix(event)
2025-04-12 14:15:07 +01:00
d786ab15c9
fix(orchestrator): better describing the note taking agent
2025-04-12 07:53:43 +01:00
47e65e1609
fix(notes): improving note taking capabilities
2025-04-12 07:48:42 +01:00
42771ea958
feat(contact-agent): linking to existing instead of creating new ones
2025-04-12 07:29:29 +01:00
77a0901352
fix: removing extra log line
2025-04-12 07:22:35 +01:00
a43efa014f
feat(log): pretty logging agent responses and tool calls
2025-04-12 07:16:30 +01:00
4990cf9c43
feat(contact-agent): working contact agent
...
Built this in under 20 minutes. Getting some really good agents
2025-04-11 21:12:06 +01:00
11c5c8921b
feat(orchestrator): async processing and ending the loop3
2025-04-09 15:23:51 +01:00
1a503c8320
fix(tool-calls): ToolLoop
2025-04-09 15:15:31 +01:00
f169fd2ba2
fix(tools): testing and processing
...
fix
2025-04-09 13:56:30 +01:00
d36dec8d60
fix(types): agent processing stuff
2025-04-09 12:12:09 +01:00
e065492dd4
feat(chat): more simplified chat messages and tool handling
2025-04-09 12:04:44 +01:00
26c6edb6ba
fixup(chat): better way to organize agent messages and tool calls
2025-04-06 20:24:40 +01:00
5c5df168ad
fix(tools): dont error if AI invested a tool
2025-04-05 15:04:09 +01:00
e101070851
refactor(tools): removing pointer map
...
This is not needed
2025-04-05 14:59:50 +01:00
5278727c51
feat(tools): return error to agent if any happened
2025-04-05 14:58:38 +01:00
9a354c38a5
test(tools): more robust multiple tool call handling
2025-04-05 14:52:31 +01:00
cd8375ce0f
test(tools): starting test suite for tools
2025-04-05 14:35:54 +01:00
