Skip to content

A rusty api for Gpt powered Agents

active 2023-10-102023-12-15 (UTC)

Partial coverage20,527 / 26,283 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-14 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
93
Pushes
68
Pull requests
0
Issues
11
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 67 days from 2023-10-10 to 2023-12-15. Pushes: 68 total, peak 14 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 11 total, peak 2 in a day. Comments: 11 total, peak 4 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
voidKandy9068011

Recent activity

Latest issues, pull requests and releases

  • Issue#16voidKandy2023-11-22 06:21
    Cool Unicode for web app
  • Issue#15voidKandy2023-11-09 00:47
    Pub interface notes
  • Issue#14voidKandy2023-11-08 19:20
    Streaming completions have broken since API update.
  • Issue#13voidKandy2023-10-27 00:43
    Observation Mode Feature
  • Issue comment#11voidKandy2023-10-22 01:14
    LTM and caching relationship improvements
  • Issue comment#8voidKandy2023-10-21 20:24
    Relationship between long and short term memory needs to be reworked
  • Issue#8voidKandy2023-10-21 20:24
    Relationship between long and short term memory needs to be reworked
  • Issue comment#11voidKandy2023-10-21 20:00
    LTM and caching relationship improvements
  • Issue comment#11voidKandy2023-10-20 00:49
    LTM and caching relationship improvements
  • Issue#11voidKandy2023-10-20 00:41
    LTM and caching relationship improvements
  • Issue comment#3voidKandy2023-10-13 18:31
    Create a way of tracking tokens from GPT responses
  • Issue comment#5voidKandy2023-10-13 18:06
    Dockerize database and configuration for easily using the long term memory feature
  • Issue#9voidKandy2023-10-13 18:05
    Configuration should be build using serde Yaml instead of config
  • Issue comment#9voidKandy2023-10-13 18:05
    Configuration should be build using serde Yaml instead of config
  • Issue#8voidKandy2023-10-13 18:05
    Relationship between long and short term memory needs to be reworked
  • Issue comment#8voidKandy2023-10-13 18:05
    Relationship between long and short term memory needs to be reworked
  • Issue#9voidKandy2023-10-12 23:51
    Configuration should be build using serde Yaml instead of config
  • Issue comment#8voidKandy2023-10-11 01:10
    Relationship between long and short term memory needs to be reworked
  • Issue#8voidKandy2023-10-11 00:29
    Relationship between long and short term memory needs to be reworked
  • Issue#7voidKandy2023-10-11 00:26
    Projects not using long_term_memory feature still require that database info be present in config/default.yaml
  • Issue comment#3voidKandy2023-10-11 00:26
    Create a way of tracking tokens from GPT responses
  • Issue comment#5voidKandy2023-10-11 00:25
    Dockerize database and configuration for easily using the long term memory feature

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.