QiJu - Development Process Diarist and Secretary of yours

QiJu is not a memory tool for agents. It is a diarist recording how a decision is made, why a direction is a dead end during every moment of a project. Its records can be accessed across projects.

Comment

Inspiration

I am an IT veteran who now is reaching 45 years old. Time and age is now silently taking my short memory. I sometimes cannot remember why I made a decision few days ago during vibe coding in a project. I started to record into a history.md file under each project that I am doing. Then I found this approach did help me in troubleshooting and bringing exprience from one project to another. Then a trend started that 'grep' search could be better than tranditional RAG. That was really interesting. At that moment, I started QiJu (which initially was called Kedu), a tool records important decision during vibe coding.

What it does

QiJu is a tool record important decision and experience during vibe coding and software development. It does not take over memory provided in Codex. QiJu holds the philosopy that codes and files are already telling what a project is about. QiJu just record how it comes to those codes and files and why it did not go to other directions.

How we built it

QiJu is a project built on Vibe Coding with agents including Codex. I spend quite a lot of time discussing the design and development documents before writing the codes. The codes are written by Codex and Claude models. Since the first version of the project, the project shows its power: the records from QiJu and project design/implementation documents together help the development can be done across different agents.

Challenges we ran into

The most important challenge of the project is to determine the type of data storage format. I have a thought if QiJu could be a product for Enterprise. I want to choose a scalable and quick searchable data format. I choosed JSONL with DuckDB because it can be migrated easily into Hadoop and S3 Tables for future Enterprise adoptions.

Accomplishments that we're proud of

Since it only includes process decisions, the storage consumption is prettey low. Its global record design allowing records from one project can be checked by another project which means exprience learnt in one project can be shared with another project regardless agents. Even a project is held for months, by reaing records from QiJu, not only know what have been developed but also can know what will be done as next time.

What we learned

  1. QiJu is an AI native tool. It can be built because Agent can be used a secretary role. A user is as a boss who tells an agent as secretary to write importand decision while the agent can record important moment during work with the user. Some agents already show priority using Qiju as handoff tool instead of its own memory mechanism.
  2. QiJu is a self-involving project. It not only keeps important reocrds of projects in which QiJu is used, but also the records can be used as live test results to improve QiJu's quality.
  3. It is good to see what a fancy product looks like, but it is also good know the journey how the product becomes fancy. QiJu focuses on this job. ## What's next for QiJu - Development Process Recorder It is recorded in QiJu project's own QiJu record: work in a collobration environment sharing records between team members.

Built With

  • chatgpt
  • claude
  • codex
  • kiro
Share this project:

Updates