PUBLIC ALPHA / built for maintainersLive repository inspection · Guided AI demo
DOCAGENT / DOCUMENTATION MAINTENANCE

Code changes.
Keep your docs in sync.

Find the documentation affected by a code change, inspect the evidence and review a focused repair. Start with a real public repository or explore the guided AI workflow.

Try the demo ↓Inspect a repository ↗View GitHub ↗
code changes. knowledge stays current.
DOCAGENTDOCUMENTATION INTELLIGENCE
Public GitHubReal commits and file diffs
6 demo stagesFrom source change to review
Human reviewYou decide what goes upstream
01 / HOW IT WORKS

From a changed API to a clear explanation.

BUILT FOR OPEN SOURCE
01

Inspect the source change

Choose a public repository and a recent commit. Read the exact files and changes returned by GitHub.

AVAILABLE NOW
02

Understand the proposed repair

Explore how a source change can map to an outdated guide, a focused patch and a translated example.

GUIDED DEMO
03

Review before publishing

Download real commit context or an example patch. AI draft generation and approved pull requests are the next milestone.

EXPORT NOW · PR FLOW PLANNED
02 / REPOSITORY WORKSPACE

Your next documentation review starts here.

PUBLIC REPOSITORY INSPECTION
LIVE / READ-ONLY

Start with a real repository.

Load the latest 10 commits from a public GitHub repository, inspect changed files and export a review context bundle.

Public repositories only. No account or wallet needed. Requests go directly to GitHub when you choose Inspect.

Ready when you are. Your repository is not connected to the guided demo.

Explore the example repository workspace DEMO DATA
REPOSITORYLANGUAGEDOC COVERAGEOPEN PATCHESSTATUS
DOCAGENT / GUIDED DEMO

Watch a code change become clear docs.

A prepared example shows how createClient(url) becomes createClient(config). Logs, checks and generated code below are simulated and stay separate from your repository inspection.

DOCAGENT / CYBER GECKO · visual source acquisition
SOURCE MONITORagent-01 / scanner
01 PATROL02 LOCATE03 STOP04 CAPTURE05 COLLECT
◉ connection.tsPATROLLING / DEMO
01// protocol-core / src/connection.ts
02export interface ConnectionConfig {
03 endpoint: string;
04 retries?: number;
05 timeout?: number;
06}
07
08export function createClient(
09 config: ConnectionConfig
10) {
11 const { endpoint, retries = 3 } = config;
12 return new RpcClient({
13 endpoint,
14 retries,
15 timeout: config.timeout ?? 5000
16 });
17}
18
19// docs / api-reference.md
20## Connection configuration
21endpoint: the RPC server URL
22retries: maximum retry attempts
23
24// source ↔ documentation mapping
25symbol: createClient
26reference: docs/api-reference.md
27status: requires maintainer review
28
29// i18n / quickstart.zh.md
30使用连接配置对象创建客户端。
31endpoint：RPC 地址
32retries：最大重试次数
33
34// next source block…
01// protocol-core / src/connection.ts
02export interface ConnectionConfig {
03 endpoint: string;
04 retries?: number;
05 timeout?: number;
06}
07
08export function createClient(
09 config: ConnectionConfig
10) {
11 const { endpoint, retries = 3 } = config;
12 return new RpcClient({
13 endpoint,
14 retries,
15 timeout: config.timeout ?? 5000
16 });
17}
18
19// docs / api-reference.md
20## Connection configuration
21endpoint: the RPC server URL
22retries: maximum retry attempts
23
24// source ↔ documentation mapping
25symbol: createClient
26reference: docs/api-reference.md
27status: requires maintainer review
28
29// i18n / quickstart.zh.md
30使用连接配置对象创建客户端。
31endpoint：RPC 地址
32retries：最大重试次数
33
34// next source block…
seeking source symbols…0 collected
crawler-01 › entering example source file
src/connection.tsWATCHING
docs/api-reference.mdQUEUED
docs/quickstart.mdQUEUED
i18n/zh/quickstart.mdQUEUED
checks/source-map.jsonQUEUED
~/docagent $ maintain --watchRUNNING
Event log SIMULATED
CURRENT OUTPUT / SOURCE EVENT
CODE STREAM · SIMULATED
0%
01/06CURRENT STAGE
0SESSION EVENTS
0DRAFT ARTIFACTS
00:00ACTIVE TIME
● GUIDED DEMO · prepared source events, no repository connectionNext: compare documentation with sourceinspect example patch ↓
03 / EXAMPLE PATCH REVIEW
See the change. Review the explanation.
protocol-core / API reference
Example source change: createClient now requires a connection configuration object.
− OUTDATED DOCUMENTATION
// Create a client with an RPC URL.
const client = createClient(rpcUrl);

Parameters:
  rpcUrl: string

Retries: not documented.
+ PROPOSED DOCUMENTATION
// Pass a connection configuration object.
const client = createClient({
  endpoint: rpcUrl,
  retries: 3
});

Parameters:
  endpoint: string — RPC endpoint
  retries?: number — maximum retry attempts
✓ symbol reference included✓ example updatedmaintainer review required
Awaiting review · local preview only; no pull request will be submitted.


Translation workspace 4 PREPARED SAMPLES
04 / LOCALIZATION
One source of truth. Multiple languages.
SAMPLE LANGUAGE PACKS
Technical identifiers stay unchanged. These prepared samples demonstrate the reading experience; no translation service is connected.


Task queue DEMO
05 / JOB ORCHESTRATION
Every task has a visible next step.
open review workspace ↗
01 / DETECTED
API signature changed
protocol-core · connection.ts
Map the change to the connection guide.
02 / DRAFTING
Usage guide update
agent-runtime · getting-started.md
Prepare a focused documentation patch.
03 / REVIEW READY
Localized quickstart
api-kit · quickstart.zh.md
Waiting for a maintainer's review.
Example task states shown for the product preview.


04 / BUILD STATUS
What works today. What comes next.
Share feedback ↗
AVAILABLE
01 — Public inspection
Repository metadata, recent commits, file diffs and downloadable review context.
DEMO READY
02 — Review experience
Six-stage walkthrough, example patch download and four prepared language samples.
NEXT
03 — Grounded AI drafts
Source-to-doc mapping, generated repairs and checks against repository evidence.
PLANNED
04 — Approved pull requests
GitHub App authorization, private repositories and maintainer-approved PR creation.


05 / QUESTIONS & ANSWERS
Know what you are trying.
What can I do right now?
Inspect a public GitHub repository, select a recent commit, read file diffs and download its review context. You can also try the separate guided documentation-maintenance demo.
Does the demo analyze my repository?
No. The demo uses prepared source events and patches. The live workspace retrieves actual GitHub data, but it does not run AI analysis or identify documentation drift automatically.
Do I need to sign in or connect a wallet?
No. Public inspection uses GitHub's unauthenticated API. Private repositories and PR creation will require a future GitHub App integration. Wallet, token and payment features are not part of this release.
What happens to repository information?
Requests go directly from your browser to api.github.com. This frontend has no project backend or analytics. Selected data stays in page memory until you navigate away; an export is saved only when you download it.
Why did my repository fail to load?
Check that it is public and has commits. GitHub limits unauthenticated requests; if the limit is reached, wait and retry. Very large or binary diffs may not include a text preview. Follow the commit link for the full GitHub view.
Can this version edit files or open pull requests?
No. Inspection is read-only, and marking the example reviewed changes only this page. The planned workflow will require maintainer approval before creating a pull request.
How can I help build DOCAGENT?
Read the project README and contribution guide, report a reproducible issue, or propose a focused improvement on GitHub.
Contribution guide ↗


KEEP KNOWLEDGE CLOSE TO CODE
Your next commit deserves up-to-date docs.
explore DOCAGENT ↑