@breviqcode/cli 0.1.0

package/dist/system-prompt.d.ts

@@ -0,0 +1,17 @@
+import type { ProjectInstructions } from "@breviqcode/core";
+import type { AgentMode, Message } from "@breviqcode/shared";
+/**
+ * Establishes what BreviqCode is and that it should actually use its
+ * tools, rather than just describe what it would do. Built in from the
+ * start this time — the Go version shipped without one for a while, and
+ * live testing found the model would produce an empty reply to something
+ * as simple as "go version" because it had no instruction that it was an
+ * agentic assistant meant to act. Never persisted to the session store;
+ * prepended fresh to the in-memory message list on every turn.
+ *
+ * `mode` is threaded through so a session started with `--plan` tells the
+ * model up front, rather than letting it discover the restriction only
+ * after a blocked tool call wastes a turn.
+ */
+export declare function systemMessage(projectRoot: string, mode?: AgentMode, instructions?: ProjectInstructions): Message;
+//# sourceMappingURL=system-prompt.d.ts.map

package/dist/system-prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"system-prompt.d.ts","sourceRoot":"","sources":["../src/system-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,kBAAkB,CAAA;AAC3D,OAAO,KAAK,EAAE,SAAS,EAAE,OAAO,EAAE,MAAM,oBAAoB,CAAA;AAE5D;;;;;;;;;;;;GAYG;AACH,wBAAgB,aAAa,CAAC,WAAW,EAAE,MAAM,EAAE,IAAI,GAAE,SAAmB,EAAE,YAAY,CAAC,EAAE,mBAAmB,GAAG,OAAO,CAoBzH"}

package/dist/system-prompt.js

@@ -0,0 +1,32 @@
+/**
+ * Establishes what BreviqCode is and that it should actually use its
+ * tools, rather than just describe what it would do. Built in from the
+ * start this time — the Go version shipped without one for a while, and
+ * live testing found the model would produce an empty reply to something
+ * as simple as "go version" because it had no instruction that it was an
+ * agentic assistant meant to act. Never persisted to the session store;
+ * prepended fresh to the in-memory message list on every turn.
+ *
+ * `mode` is threaded through so a session started with `--plan` tells the
+ * model up front, rather than letting it discover the restriction only
+ * after a blocked tool call wastes a turn.
+ */
+export function systemMessage(projectRoot, mode = "build", instructions) {
+    const modeNote = mode === "plan"
+        ? `\n\nYou are currently in PLAN MODE: only read-only tools (read_file, grep, glob, find_symbol, lsp, question) work right now — write_file, edit_file, apply_patch, and bash will be blocked. Investigate, then present your plan via exit_plan_mode once you're ready to make changes; only after the user approves it do write/execute tools become available.`
+        : "";
+    const instructionsBlock = instructions
+        ? `\n\n---\nProject instructions (from ${instructions.source} at the project root) — follow these in addition to the rules above:\n\n${instructions.content}`
+        : "";
+    return {
+        role: "system",
+        content: `You are BreviqCode, an agentic coding assistant running in a terminal, working in the project at ${projectRoot}.
+
+You have tools to read and search files (read_file, grep, glob, find_symbol, lsp), write and edit files (write_file, edit_file, apply_patch), and run shell commands (bash) in this project's directory. Use task to delegate a self-contained, read-only investigation (e.g. "find every caller of X and summarize") to a fresh sub-agent when that would keep your own context cleaner than doing the exploration yourself — not for every request, just genuinely large/independent research.
+
+Use these tools proactively whenever the request calls for it: if the user names or describes a command, run it with bash rather than only describing what it would do; if asked about code, inspect the real files instead of guessing. Write/execute tool calls may require the user's separate confirmation — that is handled automatically outside this conversation, so just make the call.
+
+Be concise and direct in your replies.${modeNote}${instructionsBlock}`,
+    };
+}
+//# sourceMappingURL=system-prompt.js.map

package/dist/system-prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../src/system-prompt.ts"],"names":[],"mappings":"AAGA;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,aAAa,CAAC,WAAmB,EAAE,OAAkB,OAAO,EAAE,YAAkC;IAC9G,MAAM,QAAQ,GACZ,IAAI,KAAK,MAAM;QACb,CAAC,CAAC,gWAAgW;QAClW,CAAC,CAAC,EAAE,CAAA;IAER,MAAM,iBAAiB,GAAG,YAAY;QACpC,CAAC,CAAC,uCAAuC,YAAY,CAAC,MAAM,2EAA2E,YAAY,CAAC,OAAO,EAAE;QAC7J,CAAC,CAAC,EAAE,CAAA;IAEN,OAAO;QACL,IAAI,EAAE,QAAQ;QACd,OAAO,EAAE,oGAAoG,WAAW;;;;;;wCAMpF,QAAQ,GAAG,iBAAiB,EAAE;KACnE,CAAA;AACH,CAAC"}

package/dist/tui/App.d.ts

@@ -0,0 +1,44 @@
+import type { AgentMode } from "@breviqcode/shared";
+/**
+ * The interactive, stay-open TUI — this project's equivalent of the Go
+ * version's Bubble Tea interface, built with Ink/React instead (matching
+ * Claude Code's own real stack, per the research behind this whole
+ * rewrite). Unlike the one-shot `breviq chat` command (send one message,
+ * stream the reply, exit), this keeps one process alive across many turns,
+ * reusing the exact same runtime wiring via `buildRuntime` — the same
+ * tools, gate, session store, symbol index, and LSP manager, just kept
+ * alive instead of torn down after one message.
+ *
+ * Tool calls render as a two-line "⏺ Label(args)" / "  ⎿ detail" block —
+ * matching Claude Code's/OpenCode's own tool-call presentation — rather
+ * than a flat status line, and the input sits in a bordered box (colored
+ * by agent mode) rather than a plain text prompt, since a bare `[build] >`
+ * line was reported live as looking nothing like either tool's actual UI.
+ *
+ * The permission-confirmation `Prompter` and the `question` tool's `Asker`
+ * are implemented as plain closures over this component's own `useState`
+ * setters — no external pub/sub bridge needed, since `buildRuntime` (and
+ * everything it constructs) is only ever built *inside* this component's
+ * effect, after Ink already owns the render tree. Gate/tools calling
+ * `prompt()`/`ask()` from deep inside a tool-call chain just resolves to
+ * "set some state and return a Promise the state-driven UI resolves later"
+ * — normal React state updates are safe to call from any async context,
+ * not just event handlers.
+ */
+export declare function App({ continueSession, initialAgentMode, resumeSessionId, }: {
+    continueSession: boolean;
+    initialAgentMode: AgentMode;
+    resumeSessionId?: string;
+}): import("react").JSX.Element;
+/**
+ * Entry point for the interactive TUI. If neither real env vars nor a
+ * saved config exist yet, runs the first-run onboarding wizard *before*
+ * Ink ever renders — `resolveConfig()` (called later, inside
+ * `buildRuntime`) would otherwise try to run that same readline-based
+ * wizard while Ink already owns stdin in raw mode, which is exactly the
+ * kind of two-consumers-fighting-over-stdin problem this project's
+ * `createInteractiveIO` fix (see CLAUDE.md) exists to avoid — simplest fix
+ * here is just not letting the two ever overlap in the first place.
+ */
+export declare function runTui(args: string[]): Promise<void>;
+//# sourceMappingURL=App.d.ts.map

package/dist/tui/App.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"App.d.ts","sourceRoot":"","sources":["../../src/tui/App.tsx"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,SAAS,EAAW,MAAM,oBAAoB,CAAA;AAqE5D;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,GAAG,CAAC,EAClB,eAAe,EACf,gBAAgB,EAChB,eAAe,GAChB,EAAE;IACD,eAAe,EAAE,OAAO,CAAA;IACxB,gBAAgB,EAAE,SAAS,CAAA;IAC3B,eAAe,CAAC,EAAE,MAAM,CAAA;CACzB,+BA6jCA;AAED;;;;;;;;;GASG;AACH,wBAAsB,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CA2B1D"}