Skip to content

armgit / ruflo

Public Imported from GitHub
0

🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated

Merge branch 'feat/console-optimizer' into feat/console-learning

ruv5346b8df279b
diff --cc plugins/ruflo-console/hooks/bindings.ts
index df9cd5fb6b,e500bd0614..0c075bfdc8
--- a/plugins/ruflo-console/hooks/bindings.ts
+++ b/plugins/ruflo-console/hooks/bindings.ts
@@@ -6,7 -6,7 +6,8 @@@ import { claimTask, handoffClaim, relea
import { EVENT_KINDS } from './data/events'
import { evolveActions } from './evolve'
import { askActions } from './ask-claude'
+import { loopActions } from './loops'
+ import { optimizerActions } from './optimizer'
import { missionActions } from './mission-control'
import { catalogActions } from './plugin-catalog'
import { saveAllowed } from './remember'
@@@ -327,7 -327,7 +328,8 @@@ export function actionsOf(state: State
settings: settingsActions(state, host, runner, (agent, text) => actions.term.ask(agent, text), () => CLI_PREFIXES[state.options.cli], () => pluginNames(state, (catalogOf(state).plugins ?? []).filter(plugin => plugin.options.length > 0).map(plugin => plugin.name))),
mission: missionActions(state, host, runner),
ask: askActions(state, host, runner, () => actions),
+ loops: loopActions(state, host, runner),
+ optimizer: optimizerActions(state, () => host.invalidate(), id => void runner.runById(id, ''), question => actions.ask.ask(question, 'overview')),
catalog: catalogActions(state, host, runner, text => actions.term.load('claude', text)),
devtools: devtoolsActions(state, host, runner.runById, why => runner.ask(null, why)),
}
diff --cc plugins/ruflo-console/hooks/views/common.ts
index 328d0c392b,adbb177454..7dad8383f8
--- a/plugins/ruflo-console/hooks/views/common.ts
+++ b/plugins/ruflo-console/hooks/views/common.ts
@@@ -4,8 -4,8 +4,9 @@@
* Text colours are theme names only, so nothing fades on a light background.
*/
import type { AskActions } from '../ask-claude'
+ import type { OptimizerActions } from '../optimizer'
import type { Attention } from './attention'
+import type { LoopActions } from '../loops'
import type { Elements, RenderChildren, RenderElement } from 'claude-code'
import type { ProbeResult } from '../data/cli'
@@@ -69,8 -69,8 +70,10 @@@ export type Actions =
evolve: EvolveActions
/** The Dev Tools view: keep a field's text, and Enter in a field runs its entry. */
devtools: DevtoolsActions
+ /** The Loop Manager (Automation): presets, the configurator, and the launcher into the Claude UI. */
+ loops: LoopActions
+ /** The Optimizer (Overview): scope, fixes (each asks first) and asking Claude about a finding. */
+ optimizer: OptimizerActions
/** Ask Claude about this section (a visible prompt or a /btw aside) or run the plugin command that fits it: each asks first. */
ask: AskActions
/** Mission Control: goal, profile, create, run next, pause/resume/cancel, auto-run, ask aside, guide Claude. */
diff --cc scripts/ci-test-baseline.txt
index cba4843b4a,9723de0a8e..8066993374
--- a/scripts/ci-test-baseline.txt
+++ b/scripts/ci-test-baseline.txt
@@@ -165,9 -165,8 +165,10 @@@ plugins/ruflo-console/tests/palette.tes
plugins/ruflo-console/tests/views.test.ts
plugins/ruflo-console/tests/labs.test.ts
plugins/ruflo-console/tests/attention.test.ts
+plugins/ruflo-console/tests/loops.test.ts
+plugins/ruflo-console/tests/learning.test.ts
plugins/ruflo-console/tests/matrix.test.ts
+ plugins/ruflo-console/tests/optimizer.test.ts
plugins/ruflo-console/tests/missions.test.ts
plugins/ruflo-console/tests/settings.test.ts
plugins/ruflo-console/tests/plugin-catalog.test.ts
diff --cc v3/docs/adr/ADR-408-ruflo-console-mission-control.md
index 8f0ed1393c,fef978c793..bdbf8c4596
--- a/v3/docs/adr/ADR-408-ruflo-console-mission-control.md
+++ b/v3/docs/adr/ADR-408-ruflo-console-mission-control.md
@@@ -85,18 -85,13 +85,28 @@@ Memory Lab's rule is now the console's
Memory Lab no longer keeps one Result block far from what was clicked. Each action records where it was raised (`memoryLab.origin`: Browse, Search, Entry, or a lab group) and its confirm (scope `mem:<area>`) and its result are drawn in a bordered panel directly under that area; the pane no longer draws that confirm at the top (`confirmInline`). An area with nothing asked or answered draws no panel. The lab groups are collapsible sections; the group of the last action stays open.
+## 12. The Loop Manager (0.15.0)
+
+A folded section at the top of the Automation page (`hooks/loops.ts`, `views/loops.ts`; Automation already owns `ruflo-loop-workers` and `ruflo-autopilot`, and every hotkey is taken, so it is a section rather than a view).
+
+- **Presets, practical to exotic** (16, in three tiers): CI watch, keep the tests green, babysit PRs, the audit and test-gap workers (practical); optimize and consolidation workers, autopilot, nightly schedule, docs sync (steady); MetaHarness drift watch, the dream-cycle flywheel (never promotes), a hive-consensus loop, the long-horizon tracker, ultralearn, swarm self-heal (exotic). Each says what a tick costs.
+- **Configurator:** interval (self-paced, 1m to 1d), task (a preset's, or typed), and a stop condition (`until 09:00`, `after 12 runs`, `when done`, or none). The exact `/loop` that will be sent is shown before anything runs, or why it cannot be sent.
+- **Launcher:** asks first, with the exact text and a note that every tick is a billed Claude Code turn and that a loop auto-expires after 7 days; yes sends one visible `/loop ...` prompt to the main Claude UI (mid-turn it only fills the prompt box), where the engine runs it as a typed command. **List / stop my loops** asks Claude to list `CronList` and pending wake-ups and to ask before stopping any.
+- **Safety:** a task that starts with `/` must be one plugin command the session lists, followed by a few plain words (a worker needs its plugin); control and bidirectional characters are stripped; a hand-typed task is screened by AIDefence (a preset is the console's own text); the stop-condition grammar is closed; the input is at most 600 characters.
+- Tests: `tests/loops.spec.ts` (grammar, builder, every preset builds, launch asks first and screens), `tests/loops.test.ts` (the section in the Automation page; a worker preset without its plugin asks nothing).
+## 13. The Learning page (0.16.0)
+
+- **Learning pulse** (`views/learning-pulse.ts`): text charts that move while the page is in front: a marker travels RETRIEVE → JUDGE → DISTILL → CONSOLIDATE (700 ms a stage), the router's model mix is a bar chart with a highlight sweeping each bar, the running success rate over the last 24 routed outcomes is a sparkline with a scanning cursor, and SONA's trajectories, patterns and signals are gauges. They draw only what was measured: no data, no chart (`n/a` says so). The frame loop asks for a redraw about three times a second while the Learning page is shown (`controller.ts`); nothing redraws while the pane is hidden or unfocused.
+- **Settings & configuration** (folded): the two switches that decide whether ruflo learns at all, `neural.enabled` and `hooks.enabled`, each a confirm-gated `ruflo config set` through the Settings actions; every other key stays in Settings.
+- **Self-learning actions** (folded, the Learning Lab's rows on this page): what was learned, training with its loss sparkline, **pretrain** at three depths (`hooks_pretrain` shallow, medium, deep: local compute that reads the repository and writes the intelligence store), **consolidate** (`agentdb_consolidate`, no options), **pattern search** (`hooks_intelligence_pattern-search`, a read) and **teach a pattern** (`hooks_intelligence_pattern-store`, a local write), and the router's route/explain/predict. Each is also `/ruflo run nn-...`. Their answers open under the button pressed (the attention panel, ADR section 11a), and the page keeps its own result block as the fallback.
+- No entry calls a paid model. Tests: `tests/learning.spec.ts` (argv, validation, headless ids), `tests/learning.test.ts` (the pulse moves over real time; the folded sections; a confirm right under the pretrain strip).
+ ## 14. The ruflo Optimizer (0.17.0)
+
+ A section at the top of the Overview (`hooks/optimizer.ts`, `views/optimizer.ts`): what is wrong or thin in this project, and a fix for each that is one confirm-gated button.
+
+ - **Findings** come only from what the console already measured, worst first: ruflo has learned nothing here yet (no patterns), the router missing too often (under 60% of 10 or more routed outcomes), no model-router state; memory not checked this session, many memories with no vector (under 60% of the newest listed), a second memory store outside the counts, a store large enough to compact; where the time goes not measured; every alert the console already raises (stalled agent, expired claim, stale marketplace, daemon stopped, mods not seated, budget); and the full health check. An unread store is a finding to check, never a verdict.
+ - **Fixes are existing palette entries**, so the Optimizer adds no new way to write: pretrain at shallow or medium depth, train, quantize, consolidate, compress, plan a cleanup, initialise embeddings, rebuild the RaBitQ index, optimise, doctor with and without `--fix`. Each asks first (a read runs at once) and says what it does. A test fails if a fix names an entry the palette does not have.
+ - **Scope** limits which fixes are offered: *safe* (reads and light upkeep), *balanced* (local compute that writes ruflo's own stores), *deep* (heavier rebuilds, and anything that may fetch a model).
+ - **Before and after:** pressing a fix remembers the finding's metric (`vectors 1/5`, `patterns n/a`); the line under the finding reads before → now and says when the finding is gone. **✦ ask Claude** words the finding and sends it to the main Claude UI (it asks first).
+ - **Answers** open under the fix button pressed (the attention panel, section 11a): the confirm, then the result lines of the command that ran, with the Overview's own result block as the fallback.
+ - Tests: `tests/optimizer.spec.ts` (what is found, scopes, every fix a real palette entry, before/after), `tests/optimizer.test.ts` (the section in the Overview; a fix's confirm sits under its finding; nothing runs before yes).