© 2005 gh555.com All Rights Reserved.

qqq IDE Development Progress since 2026.05.16

qqq IDE is an open-source IDE project based on VS Code, Code-OSS, and VSCodium.

The core idea of qqq is simple:

Make everything pasteable.

qqq lets users paste images, screenshots, files, folders, HTML pages, videos, media resources, documents, and mixed creative materials directly into the editor, with WYSIWYG preview.

But qqq is not only a paste extension.

Paste is only the entry point.

The long-term goal of qqq IDE is to create a new way to orchestrate ideas inside the IDE, making the editor behave more like an operating system for developers, writers, creators, researchers, and AI tool users.

Useful links:

• GitHub Repository / README: https://github.com/gh555com/qqq
• qqq IDE Roadmap: https://github.com/gh555com/qqq/discussions/6
• Official Download: https://www.gh555.com/qqq

---

2026.06.07 —

---

## 2026.06.07 — Three work areas (left, middle, right) start working simultaneously.

qqq IDE is running at full speed, and its own development is carried out within qqq IDE.

---

## 2026.06.05 — Within the same floor, you can prompt the AI immediately without creating a new floor.

Once your message is sent and the AI is halfway through processing it, you may spot errors in your input and want to redirect the AI right away without interrupting it. The qqq IDE supports this functionality and is rigorously engineered to guarantee such capability.

---

## 2026.06.02 — Liberation: qqq IDE enables simultaneous opening of three AI chat panels, with the three sandboxes operating independently and continuously without mutual interference.

The multi-instance AI task feature native to qqq IDE was developed using qqq IDE itself; in other words, qqq IDE efficiently bootstrapped its own development.

---

## 2026.05.30 — qqq IDE can run long-running tasks without interruption.

--- qqq IDE

2026.05.30 — What is qz? Why does it exist?

Think of qz as the entire application's "courier company."

Before qz

Every module spawned its own child processes — scattered child_process.exec calls:

AI panel     → spawn bash       (no timeout)
File manager → spawn rg         (no timeout)
Editor       → spawn python     (no timeout)
LSP          → spawn typescript (no timeout)

The problem: one command hangs → nobody kills it → orphan process sits in memory and keeps running forever. Like ordering food delivery where nobody delivers and nobody cancels — the rider is just out there indefinitely.

What qz does

All child processes go through a single entry point, with three layers of protection built in:

Every spawn ships with:
┌─────────────────────────────────┐
│ ① deadline hard timeout        │  30s reached → kill entire process tree
│ ② stall no-output timeout      │  5s no activity → kill
│ ③ tree-kill full cleanup       │  kill parent and all children, no orphans left
└─────────────────────────────────┘

Three-tier runner fallback: ghrun (Rust, fastest) → runner (Python, fallback) → node (last resort)

Why it's called the "Truth Machine"

Because it's the only entry point. No spawn can escape qz's watch. All the old scattered child_process.spawn calls have been refactored away. Now when you read the logs, the [qz] prefix is the universal passport. 🎯

---

2026.05.29 — Building AI Infrastructure from Scratch：https://github.com/gh555com/qqq-IDE

2026.05.29 has been open-sourced.

---

2026.05.28 — There are two color schemes in total.

Today, we built the underlying "qgs" and "qg" data persistence engines. Meanwhile, we introduced the concept of a root folder for the AI viewport, and completed the initial prototype for persisting AI conversation records: hot data is stored in quest.sq3 based on "qgs" (located in the root folder directory of the AI viewport), while locally archived cold data relies on "qg".

---

2026.05.26 — Today marks my first day developing with the qqq IDE on my own, working on an extremely large project with a massive context window.

---

2026.05.25 — qqq IDE has decided to break away from the VSCodium ecosystem and build a 100% self‑developed AI IDE from scratch. We will never forget our original aspiration: to paste everything.

Arrange all creative ideas, and deliver a more efficient AI‑powered programming tool.

---

2026.05.22 — Server-side Hot Update Module

---

2026.05.22 — The scaffolding for development and compilation is operating normally.

A development and loading model centered around “gaea-loader” will be established to enhance the efficiency of both first-party and third-party developers, with the goal of achieving hot-updates for everything.

---

2026.05.18 — Image content recognition: it actually found it！

---

2026.05.17 — Rage Meter: a core innovation for AI IDE workflows

Concept summary:

plaintext
User question
    │
    ▼
Pro + max rage 100 takes a first look
    │ Output:
    │ ① task breakdown
    │ ② information collection checklist
    │ ③ rage value allocation for each subtask
    │
    │ This step is cheap.
    │ It is only a short planning prompt.
    ▼
Flash + disabled rage 0 collects information
    │ Uses tools, reads files, searches code,
    │ and follows the instructions from Pro.
    ▼
Pro / Flash executes subtasks based on assigned rage values
    │ Simple rename      → Flash rage 0
    │ Core algorithm     → Pro high rage 70
    │ Architecture choice → Pro max rage 100
    ▼
Final output to the user
---

## 2026.05.16 — qqq IDE started to exist. GE billing.


On 2026.05.16, qqq IDE started to exist as a real product direction.

Before this point, qqq was mainly an extension that improved paste workflows inside VS Code, Code-OSS, and VSCodium.

After this point, qqq started moving toward qqq IDE.

The direction became clearer:

> Make everything pasteable.  
> Orchestrate ideas.  
> Turn the IDE into an operating system.

The goal is to reduce the distance between seeing something, capturing it, organizing it, and using it.

This was the first development snapshot of qqq IDE.

thank you for watching！