@aitne-sh/aitne 0.1.11 → 0.1.13

package/agent-assets/docs/pages/git.md

@@ -0,0 +1,73 @@
+---
+schema_version: 1
+slug: pages/git
+title: "Git Page"
+id: page-git
+aliases:
+  - git page
+  - repositories page
+category: pages
+summary: |
+  The Git page configures how the agent watches each registered
+  repository — polling cadence, automation triggers, and the daily git
+  management the morning routine performs. Repositories are registered on
+  the Connections page.
+tags:
+  - git
+  - lifestyle
+status: stable
+ask_examples:
+  - What can I do on the Git page?
+  - How do I change how often the agent checks a repo?
+  - Where do I set up automation triggers for a repository?
+  - How do I add a repository?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - git
+  - repositories
+  - polling
+  - triggers
+  - daily management
+related:
+  - features/lifestyle/git
+  - features/integrations/git
+  - features/integrations/github
+ui_anchors:
+  - /git
+---
+
+# Git Page
+
+The `/git` page is where you fine-tune how the agent handles each
+repository you've registered. Every registered repo shows three
+collapsible sections.
+
+## What you can do here
+
+- **Polling** — how often the agent checks the repo for changes.
+- **Triggers** — automation rules that start follow-up work when a change
+  matches a rule you set.
+- **Daily git management** — the routine upkeep the morning routine runs
+  on the repo each day.
+
+You add repositories on the Connections page
+(`/connections/repositories`), not here. If you haven't registered any
+yet, this page just shows a "No repositories registered" prompt that links
+you there.
+
+## Where to go deeper
+
+- [Git (lifestyle)](../features/lifestyle/git.md) — how the agent watches
+  and reports on your repos.
+- [Git integration](../features/integrations/git.md) — registering and
+  authenticating repositories.
+- [GitHub integration](../features/integrations/github.md) — the GitHub
+  side (PRs, issues).
+
+## Related
+
+- [Connections page](connections.md) — register repositories here first.
+- [Agents page](agents.md) — the morning routine that runs daily git
+  management.

package/agent-assets/docs/pages/knowledge.md

@@ -0,0 +1,75 @@
+---
+schema_version: 1
+slug: pages/knowledge
+title: "Knowledge Page"
+id: page-knowledge
+aliases:
+  - knowledge page
+  - memory page
+  - context files page
+category: pages
+summary: |
+  The Knowledge page is where the agent's memory lives — the Markdown
+  context files it reads and writes, the skills it runs, plus activity,
+  entities, and a way to upload your own knowledge files.
+tags:
+  - knowledge
+  - memory
+  - skills
+status: stable
+ask_examples:
+  - What can I do on the Knowledge page?
+  - Where do I edit what the agent knows about me?
+  - Where are the agent's skills?
+  - How do I upload a file into the agent's knowledge?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - knowledge
+  - memory
+  - context files
+  - skills
+  - entities
+  - upload
+related:
+  - concepts/memory-model
+  - concepts/skills
+  - features/memory-files/user-profile
+  - guides/import-knowledge-file
+ui_anchors:
+  - /knowledge
+---
+
+# Knowledge Page
+
+The `/knowledge` page is your window into the agent's memory and skills.
+It has five tabs.
+
+## What you can do here
+
+- **Context Files** — browse and edit the plain-Markdown files the agent
+  reads and writes (identity/profile, state/today, journals, and more).
+- **Skills** — review the skills the agent can run and how they're wired.
+- **Activity** — see recent reads and writes against the knowledge store.
+- **Entities** — the people, projects, and things the agent has extracted.
+- **Upload** — add your own file into the agent's knowledge.
+
+Tip: the `?` on each tab opens the concept doc for that tab specifically
+(memory model, skills, or the import guide).
+
+## Where to go deeper
+
+- [Memory model](../concepts/memory-model.md) — the file layout and the
+  rules around it.
+- [Skills](../concepts/skills.md) — how skills and the self-learning loop
+  work.
+- [User profile file](../features/memory-files/user-profile.md) — what the
+  agent knows about you.
+- [Import a knowledge file](../guides/import-knowledge-file.md) — the
+  upload flow end to end.
+
+## Related
+
+- [Wiki page](wiki.md) — a separate, workspace-scoped knowledge builder.
+- [Settings page](settings.md) — Self-learning and Management live there.

package/agent-assets/docs/pages/overview.md

@@ -0,0 +1,90 @@
+---
+schema_version: 1
+slug: pages/overview
+title: "Overview Page"
+id: page-overview
+aliases:
+  - overview page
+  - home page
+  - dashboard home
+  - landing page
+category: pages
+summary: |
+  The Overview is the dashboard home — your agent at a glance. It shows
+  current status, what needs your attention, today's activity and spend,
+  and shortcuts into the rest of the app.
+tags:
+  - dashboard
+status: stable
+ask_examples:
+  - What can I do on the Overview page?
+  - Where do I approve something the agent is waiting on?
+  - How do I trigger an activity scan right now?
+  - Where do I see today's cost on the dashboard?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - overview
+  - home
+  - status
+  - approvals
+  - run now
+related:
+  - pages/activity
+  - pages/analytics
+  - concepts/agent-day
+  - features/operations/approvals
+  - features/operations/activity-and-conversations
+ui_anchors:
+  - /
+---
+
+# Overview Page
+
+The landing screen at `/`. It answers "is my agent OK, and does anything
+need me right now?" without making you dig through the other pages.
+
+## What you can do here
+
+- **See what needs attention.** System warnings and pending
+  [approvals](../features/operations/approvals.md) surface at the top and
+  can be approved or rejected inline. Both are hidden when there is
+  nothing to act on.
+- **Read the status bar.** Current agent state, the next scheduled
+  activity scan (with a **Run now** button to trigger it immediately),
+  and today's spend.
+- **Skim recent activity.** A live feed of the latest agent events — jump
+  to the [Agent Log](activity.md) for the full history.
+- **Glance at today's context.** Calendar preview, drafts awaiting your
+  review, a health summary, and a cost summary card.
+- **Jump into your life.** "Your Life" shortcuts and a rotating capability
+  tip link out to Knowledge, Wiki, Reading, and more.
+
+## Where to go deeper
+
+- [The agent's day](../concepts/agent-day.md) — how routines, scans, and
+  quiet hours shape what you see here.
+- [Approvals](../features/operations/approvals.md) — when the agent asks
+  before acting.
+- [Activity & Conversations](../features/operations/activity-and-conversations.md)
+  — the full audit trail behind the recent-events feed.
+- [Costs & quotas](../concepts/costs-and-quotas.md) — what the spend
+  numbers mean.
+
+## Related
+
+Every other dashboard page, all reachable from here:
+
+- [Chat page](chat.md)
+- [Agents page](agents.md)
+- [Tasks page](tasks.md)
+- [Agent Log page](activity.md)
+- [Analytics page](analytics.md)
+- [Knowledge page](knowledge.md)
+- [Wiki page](wiki.md)
+- [Reading page](reading.md)
+- [Browser page](browser.md)
+- [Git page](git.md)
+- [Connections page](connections.md)
+- [Settings page](settings.md)

package/agent-assets/docs/pages/reading.md

@@ -0,0 +1,65 @@
+---
+schema_version: 1
+slug: pages/reading
+title: "Reading Page"
+id: page-reading
+aliases:
+  - reading page
+  - books page
+  - highlights page
+category: pages
+summary: |
+  The Reading page is your reading list built from Kindle — import your
+  My Clippings.txt, then browse books (filterable by status) and the
+  highlights the agent extracted.
+tags:
+  - reading
+  - lifestyle
+status: stable
+ask_examples:
+  - What can I do on the Reading page?
+  - How do I import my Kindle highlights?
+  - Where do I see my book highlights?
+  - How do I filter books I've finished?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - reading
+  - books
+  - highlights
+  - kindle
+  - clippings
+related:
+  - features/lifestyle/reading
+ui_anchors:
+  - /reading
+---
+
+# Reading Page
+
+The `/reading` page gathers your Kindle reading into one browsable
+list, split across two tabs.
+
+## What you can do here
+
+- **Import My Clippings.txt** with the button in the header (connect your
+  Kindle via OpenMTP or the Send-to-Kindle app first). After the first
+  upload, new highlights arrive on their own through the Kindle Notebook
+  Export email pipeline — Kindle emails your exported notes and the agent
+  imports them for you.
+- **Books tab** — every book, filterable by status (All, Reading,
+  Completed, Abandoned).
+- **Highlights tab** — the individual highlights extracted from your
+  clippings.
+
+## Where to go deeper
+
+- [Reading](../features/lifestyle/reading.md) — how the Kindle import and
+  highlight sync work, and how the agent uses them.
+
+## Related
+
+- [Knowledge page](knowledge.md) — where longer-lived notes live.
+- [Overview page](overview.md) — Reading is one of the "Your Life"
+  shortcuts.

package/agent-assets/docs/pages/settings.md

@@ -0,0 +1,77 @@
+---
+schema_version: 1
+slug: pages/settings
+title: "Settings Page"
+id: page-settings
+aliases:
+  - settings page
+  - settings hub
+  - preferences page
+category: pages
+summary: |
+  The Settings page is the configuration hub. The landing tab covers the
+  agent's identity and management mode; a sidebar groups the rest —
+  Profile, Intelligence, Operations, Browser, and System.
+tags:
+  - config
+status: stable
+ask_examples:
+  - What can I do on the Settings page?
+  - Where do I change the agent's name or character?
+  - Where do I set quiet hours?
+  - Where do I change which model handles a tier?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - settings
+  - configuration
+  - models
+  - hours
+  - safety
+related:
+  - concepts/agent-day
+  - concepts/backends-and-tiers
+  - features/operations/quiet-hours
+  - concepts/safety-and-execution
+ui_anchors:
+  - /settings
+---
+
+# Settings Page
+
+The `/settings` landing (**Agent**) covers the basics — the agent's display
+name, its character, management mode, and vault health. A sidebar groups
+everything else.
+
+## What you can do here
+
+- **Profile** — **Agent** (name, character, management mode) and
+  **Hours & Notifications** (quiet hours, notification policy).
+- **Intelligence** — **Models** (which model serves each tier — the
+  agent's speed/cost levels),
+  **Self-learning** (skill-overlay review), **Lessons** (the feedback
+  learning store), and **Wiki** (workspace configuration).
+- **Operations** — **Management** (the agent's primary vault + management
+  mode) and **Commands** (settings for bang-commands — the `!`-prefixed
+  shortcuts you type in chat).
+- **Browser** — **Browser History** and **Browser Automation** settings
+  (mirrored on the [Browser page](../pages/browser.md)).
+- **System** — **Safety** (tool policy), **Infrastructure** (config keys,
+  paths), and **Danger Zone** (reset and reinstall).
+
+## Where to go deeper
+
+- [The agent's day](../concepts/agent-day.md) — hours and routines.
+- [Backends & tiers](../concepts/backends-and-tiers.md) — what the Models
+  page controls.
+- [Quiet hours](../features/operations/quiet-hours.md) — when the agent
+  stays silent.
+- [Safety & execution](../concepts/safety-and-execution.md) — what the
+  Safety page governs.
+- [Config reference](../reference/config.md) — every editable key.
+
+## Related
+
+- [Agents page](agents.md) — per-agent schedules and rulebooks.
+- [Connections page](connections.md) — link outside services.

package/agent-assets/docs/pages/tasks.md

@@ -0,0 +1,74 @@
+---
+schema_version: 1
+slug: pages/tasks
+title: "Tasks Page"
+id: page-tasks
+aliases:
+  - tasks page
+  - task board
+  - queue page
+  - schedule page
+category: pages
+summary: |
+  The Tasks page is the operations hub — everything the agent has in
+  motion. A standing Board of work items, a run Queue (upcoming and
+  history), and your recurring Scheduled DMs, all in your timezone.
+tags:
+  - agents
+  - scheduler
+status: stable
+ask_examples:
+  - What can I do on the Tasks page?
+  - Where do I see what the agent is about to run?
+  - How do I set up a recurring DM reminder?
+  - Where did the Schedule page go?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - tasks
+  - queue
+  - schedule
+  - scheduled dms
+  - board
+related:
+  - pages/agents
+  - features/memory-files/schedule
+  - features/operations/schedule-approaching
+  - concepts/routines
+ui_anchors:
+  - /tasks
+---
+
+# Tasks Page
+
+The `/tasks` page is where the standing work, the run queue, and your
+scheduled DMs all live. (The old **Schedule** page merged in here — its
+queue and DM rules are now the Queue and Scheduled DMs tabs.)
+
+## What you can do here
+
+- **Board tab** — the read-only Unified Task Board: a live inventory of
+  everything in motion (agents, triggers, runs, background workers), each
+  clickable for detail.
+- **Queue tab** — the concrete runs your schedules produce. **Upcoming**
+  lists what is about to run, soonest first; **History** shows what already ran.
+- **Scheduled DMs tab** — the home for recurring DM rules (the reminders
+  and nudges). Create, edit, and remove them here.
+- **Status strip** at the top shows the next scheduled run.
+
+All times render in your own timezone.
+
+## Where to go deeper
+
+- [The schedule memory file](../features/memory-files/schedule.md) — how
+  scheduled work is stored.
+- [Schedule approaching](../features/operations/schedule-approaching.md) —
+  the heads-up the agent gives before a run.
+- [Routines](../concepts/routines.md) — the recurring agents that feed the
+  queue.
+
+## Related
+
+- [Agents page](agents.md) — the identities behind the runs.
+- [Overview page](overview.md) — the next run also shows on the home status bar.

package/agent-assets/docs/pages/wiki.md

@@ -0,0 +1,73 @@
+---
+schema_version: 1
+slug: pages/wiki
+title: "Wiki Page"
+id: page-wiki
+aliases:
+  - wiki page
+  - wiki dashboard
+category: pages
+summary: |
+  The Wiki page is the dashboard for the personal wiki builder — an opt-in
+  workspace that turns URLs, pastes, and notes you DM into a linked
+  Markdown wiki. It shows the index and recent activity, or an enable
+  prompt when no workspace exists yet.
+tags:
+  - wiki
+  - knowledge
+status: stable
+ask_examples:
+  - What can I do on the Wiki page?
+  - How do I enable the wiki?
+  - Where do I see my wiki's articles?
+  - How do I add a source to my wiki?
+locale: en-US
+created: 2026-07-01
+updated: 2026-07-01
+keywords:
+  - wiki
+  - workspace
+  - ingest
+  - compile
+  - articles
+related:
+  - features/wiki/overview
+  - features/wiki/dashboard
+  - features/wiki/commands
+  - guides/build-your-wiki
+ui_anchors:
+  - /wiki
+---
+
+# Wiki Page
+
+The `/wiki` page is where you read your wiki — the view surface for the
+wiki builder. You build the wiki itself over DM. The wiki is opt-in: until
+you enable a workspace, the page shows a **Wiki not enabled** card with a
+prompt to turn it on.
+
+## What you can do here
+
+- **Enable a workspace** the first time, from the enable card.
+- **Browse the index** of synthesized articles once a workspace is active.
+- **Watch recent activity** — the latest captures, compiles, and answers.
+- **Build the wiki over DM.** The real work happens through bang commands
+  (messages that start with `!`) you send the agent: `!ingest` to capture,
+  `!compile` to synthesize, `!ask` for cited answers, and
+  `!lint` / `!trace` / `!connect` to audit, trace history, and bridge
+  domains.
+
+## Where to go deeper
+
+- [Wiki overview](../features/wiki/overview.md) — the workspace concept and
+  the `00_inbox` / `10_raw` / `20_wiki` / `30_outputs` layers.
+- [Wiki dashboard](../features/wiki/dashboard.md) — this page and the
+  timeline in detail.
+- [Wiki commands](../features/wiki/commands.md) — the full `!` reference.
+- [Build your wiki](../guides/build-your-wiki.md) — first-day walkthrough.
+
+## Related
+
+- [Knowledge page](knowledge.md) — the agent's own memory (distinct from
+  the wiki).
+- [Settings → Wiki](settings.md) — workspace configuration.

package/agent-assets/docs/reference/api.md

@@ -16,9 +16,6 @@ summary: |
   per-route files under packages/daemon/src/api/routes/.
 section: api
 tags:
-  - reference
-  - api
-  - core
   - operations
 status: stable
 ask_examples:
@@ -28,7 +25,7 @@ ask_examples:
   - How do I list registered backends?
 locale: en-US
 created: 2026-04-25
-updated: 2026-06-08
+updated: 2026-07-01
 keywords:
   - API
   - REST
@@ -50,20 +47,23 @@ related:
 
 # API Reference
 
-The daemon serves a single Hono app on `127.0.0.1:PA_API_PORT` (default
-`8321`). Almost all endpoints are mounted under `/api/*`; the lone
-exception is the GitHub webhook receiver, mounted at root `/webhook/github`.
+The daemon serves one Hono web app on `127.0.0.1:PA_API_PORT` (default
+`8321`). Hono is a small, fast HTTP framework. Almost every endpoint sits
+under `/api/*`; the one exception is the GitHub webhook receiver, at the
+root path `/webhook/github`.
+
 **Source of truth:** `packages/daemon/src/api/server.ts` (`createApp`)
-registers most route groups, with one post-compose mount in
-`packages/daemon/src/bootstrap/api.ts` (the docs corpus + docs-QA, wired
-only after the indexer handle exists). Each group lives in its own file
-or directory under `packages/daemon/src/api/routes/`.
+registers most route groups. One more group is mounted later, in
+`packages/daemon/src/bootstrap/api.ts` — the docs corpus plus docs-QA,
+which can only be wired up once the search indexer is ready. Each group
+lives in its own file or directory under `packages/daemon/src/api/routes/`.
 
 ## Auth
 
-A bearer token is generated at first launch and stored in the OS
-keychain. The dashboard reads it via the daemon proxy; external
-callers pass it as `Authorization: Bearer <token>`.
+A bearer token — a secret string that proves a caller is allowed to use
+the API — is generated at first launch and stored in the OS keychain. The
+dashboard reads it through the daemon proxy; external callers pass it in
+the `Authorization: Bearer <token>` header.
 
 ## Route Groups
 
@@ -187,9 +187,10 @@ keys.
 ## Risk classification
 
 Every endpoint carries a `RiskTier` from
-`packages/daemon/src/safety/risk-classifier.ts`. The enum has three
-values (the former **notify** tier was abolished daemon-wide — Approve
-now covers everything that used to be Notify):
+`packages/daemon/src/safety/risk-classifier.ts` that says how much
+protection it needs. There are three values (the former **notify** tier
+was removed daemon-wide — Approve now covers everything that used to be
+Notify):
 
 - **autonomous** — safe to execute without any auth or notification.
 - **read_sensitive** — touches personal data (email, calendar, notes,

package/agent-assets/docs/reference/cli-commands.md

@@ -14,8 +14,6 @@ summary: |
   dashboard, plus the environment variables that override defaults.
 section: cli
 tags:
-  - core
-  - reference
   - cli
   - operations
 status: stable
@@ -28,7 +26,7 @@ ask_examples:
   - How do I check my install with aitne doctor?
 locale: en-US
 created: 2026-04-27
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - aitne start
   - aitne stop
@@ -54,6 +52,7 @@ related:
   - features/messaging/bang-commands
   - reference/knowledge-layout
   - reference/config
+  - reference/keyboard-shortcuts
 ui_anchors:
   - /setup
   - /activity
@@ -66,10 +65,11 @@ ui_anchors:
 
 `aitne` is the project's CLI (`bin/aitne.mjs`). The `pnpm <cmd>` forms are
 workspace scripts that delegate to the same entry point. Use whichever you
-prefer — `aitne start` and `pnpm start` do the same thing. After installing
-the npm package globally (`npm install -g @aitne-sh/aitne`) the `aitne`
-binary is on your `$PATH` and you no longer need to be inside the repo to
-use it. The tables below show both forms.
+prefer — `aitne start` and `pnpm start` do the same thing. After you install
+the npm package globally (`npm install -g @aitne-sh/aitne`), the `aitne`
+binary lands on your `$PATH` (the list of folders your shell searches for
+commands), so you can run it from anywhere — you no longer need to be inside
+the repo. The tables below show both forms.
 
 Note: `pnpm build` is *not* the same as `aitne build`. `pnpm build` runs
 `turbo run build` directly; `aitne build` runs the same build **and** writes
@@ -157,9 +157,10 @@ lives under `PA_DATA_DIR`, **not** inside the repo.
 
 ## Where data lives
 
-The context vault is partitioned into six authority classes (context-vault
-v2). The agent never writes these files directly — it goes through the
-daemon at `http://localhost:8321/api/context/<class>/<path>`.
+The context vault is split into six top-level folders (context-vault v2),
+each one an "authority class" — a separate group of memory files. The agent
+never writes these files directly; every write goes through the daemon at
+`http://localhost:8321/api/context/<class>/<path>`.
 
 ```
 ~/.personal-agent/
@@ -182,3 +183,5 @@ daemon at `http://localhost:8321/api/context/<class>/<path>`.
   guide that uses these commands end-to-end.
 - [Reinstall Cleanly](../guides/reinstall-cleanly.md) — when you need
   to wipe state and start over.
+- [Keyboard Shortcuts](./keyboard-shortcuts.md) — the dashboard hotkeys
+  that pair with these terminal commands.