Frontend enabling work by foolishsailor · Pull Request #26 · eumemic/ai-legion

foolishsailor · 2023-04-16T22:50:28Z

BE moved in agents-controller folder
frontend repo using react and vite created
devops yml updated to run/build both repos
proof of concept streaming of messages displayed in list in FE
send messages to agents from FE

Ready for merge will be merging this locally with my dev branch and start a new branch to add a control bar with buttons etc for things like: stop/start agent, add ability to clikc an agent and send message to that agent etc

foolishsailor · 2023-04-16T22:52:54Z

judging by all the red above ill have to sort the yml...

rafalzawadzki · 2023-04-17T13:38:40Z

@@ -0,0 +1,131 @@
+import React, { useEffect, useState } from 'react';


Just a typo in file name ;)
frontend/src/components/agentStream.tsx

…ent lists

…saging without burning tokens

eumemic

Thanks! This mostly looks good but I think there's some unnecessary changes included here.

eumemic · 2023-04-19T23:31:35Z

+    ecmaFeatures: {
+      jsx: true,
+    },


We don't need this any more since you moved the actual frontend code out, right?

Suggested change

ecmaFeatures: {

jsx: true,

},

yep leftt over will remove

eumemic · 2023-04-19T23:31:53Z


 jobs:
-  build:
+  build_agent_controller:


Can we revert this?

Suggested change

build_agent_controller:

build:

will revert

eumemic · 2023-04-19T23:32:13Z

-        node-version: [14.x, 16.x, 18.x]
+        node-version: [16.x, 18.x]


Curious why node 14 is no longer supported?

wasnt building in CI/CD due to my machine creating a newer version of lockfile?

eumemic · 2023-04-19T23:32:25Z


      - name: Install dependencies
-        run: npm ci
+        run: npm i


Why this change?

eumemic · 2023-04-19T23:36:32Z


 ```
-npm run start [# of agents] [gpt-3.5-turbo|gpt-4]
+npm run start agents=[# of agents] model=[gpt-3.5-turbo|gpt-4] test=[true|false]


This seems like the only change in this file that's relevant to this PR, can we revert the rest? In particular I don't understand why you removed the part at the top with the discord link or the action errors section.

Ahh shite - that was unintentional - I had split our the readme to the parent readme for the rpo - which contained all the info like the disord linked and it had two links to the backend readme and the frontend readme. This was just the backend readme. It needs to be reintegrated with the monorepo readme

eumemic · 2023-04-19T23:41:14Z

+    if (test) {
+      generateObjectEveryTwoSeconds();
+    }


Something about this leaves a bad taste in my mouth. I'd rather not have the core code responsible for generating test data based on a CLI parameter. Rather, it would be better if we could stand up a normal server and then have an external test script pump in fake data if we want to run tests.

im ok with this, this was a quick and easy process to help build the FE without a mock data server running. Will remove

eumemic · 2023-04-20T21:08:09Z

+### Agent state
+
+Each agent stores its state under the `.store` directory. Agent 1, for example has
+
+```
+.store/1/memory
+.store/1/goals
+.store/1/notes
+```
+
+You can simply delete any of these things, or the whole agent folder (or the whole `.store`) to selectively wipe whatever state you want between runs. Otherwise agents will pick up where you left off on restart.
+
+A nice aspect of this is that when you want to debug a problem you ran into with a particular agent, you can delete the events in their memory subsequent to the point where the problem occurred, make changes to the code, and restart them to effectively replay that moment until you've fixed the bug. You can also ask an agent to implement a feature, and once they've done so you can restart, tell them that you've loaded the feature and ask them to try it out.
+


Somehow this duplicate content got added to the top of the README now.

Suggested change

### Agent state

Each agent stores its state under the `.store` directory. Agent 1, for example has

```

.store/1/memory

.store/1/goals

.store/1/notes

```

You can simply delete any of these things, or the whole agent folder (or the whole `.store`) to selectively wipe whatever state you want between runs. Otherwise agents will pick up where you left off on restart.

A nice aspect of this is that when you want to debug a problem you ran into with a particular agent, you can delete the events in their memory subsequent to the point where the problem occurred, make changes to the code, and restart them to effectively replay that moment until you've fixed the bug. You can also ask an agent to implement a feature, and once they've done so you can restart, tell them that you've loaded the feature and ask them to try it out.

eumemic · 2023-04-20T21:11:51Z

+      const t0 = Date.now();
+      this.messageBus.send(
+        messageBuilder.agentToAgent(
+          this.id,
+          [AGENT_ID],
+          `Reflecting on ${events.length} events...`
+        )
+      );
+
      const actionText = await makeDecision(events);

+      this.messageBus.send(
+        messageBuilder.agentToAgent(
+          this.id,
+          [AGENT_ID],
+          `Arrived at a decision after ${((Date.now() - t0) / 1000).toFixed(
+            1
+          )}s  \n\n ${actionText}`
+        )
+      );
+


I don't think we need to send these as messages to the control agent. If the user is interested in when the agent is thinking they will presumably be using your UI to monitor it.

foolishsailor added 4 commits April 16, 2023 20:41

move existing repo to agents folder and update devops

ca8b4e7

initial project

466ab7b

proof of concept and tooling

a8e73b3

proof of concept and tooling done

46218a0

added readme

62f6a55

rafalzawadzki reviewed Apr 17, 2023

View reviewed changes

foolishsailor added 11 commits April 17, 2023 15:11

added reflecting and decision dialogue to bus

cc7a0b7

added reflecting and decision dialogue to bus

e682c5d

added reflecting and decision dialogue to bus

d073356

added agent split components

f046ad7

WIP

4dd036f

added ability to send messages

6202139

touch up css

da3a32f

refactorFE to best practice, tidy up css and add scroll to end for ag…

901fcdd

…ent lists

fix type in yml

2591a00

fix yml directories for repos

5afe5b2

added default directories to jobs

b74929a

foolishsailor marked this pull request as ready for review April 18, 2023 14:04

foolishsailor added 11 commits April 18, 2023 15:37

small fix to agent height calc

664c72e

last css fix

1fdaaf6

fix indent in yml

79d1a58

setup basic testing infra

ce53407

finish infra for testing and add linting

1657a4d

allow warnings

d8dd64c

remove unsupported node for FE

40324df

remove fe from repo

cdbc189

merge conflict

caeb513

revert github actions back to old version

11d1af5

new package.lock generated

e2f74c2

foolishsailor added 6 commits April 19, 2023 08:38

remove old working directory in yml

39396c8

change to node 14 lowest supported

77eb392

added help and test to console parameters to allow testing agents mes…

8fa2be1

…saging without burning tokens

updated readme

34fb6d2

add test flag to web socket server

7ec2370

fix lint issue

ec247a7

eumemic changed the title ~~Fe initial setup~~ Frontend enabling work Apr 19, 2023

eumemic requested changes Apr 19, 2023

View reviewed changes

foolishsailor added 4 commits April 20, 2023 10:19

prResponse

9cbe954

revert github actions

b7e2a70

lint, test, format

1dafb41

removed the test param from return of parameters

2baeaed

eumemic requested changes Apr 20, 2023

View reviewed changes

		@@ -0,0 +1,131 @@
		import React, { useEffect, useState } from 'react';

Conversation

foolishsailor commented Apr 16, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

foolishsailor commented Apr 16, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eumemic left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

foolishsailor commented Apr 16, 2023 •

edited

Loading