https://docs.nocfoundry.dev/dev/reference/Recent content in Reference on NOCFoundry DocsHugoenhttps://docs.nocfoundry.dev/dev/reference/cli/Mon, 01 Jan 0001 00:00:00 +0000https://docs.nocfoundry.dev/dev/reference/cli/<h1 id="cli-reference">CLI Reference</h1> <p>The root command is:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">nocfoundry </span></span></code></pre></div><p>Core entry points include:</p> <ul> <li><code>nocfoundry invoke</code></li> <li><code>nocfoundry skills-generate</code></li> <li><code>nocfoundry --ui</code></li> </ul> <h2 id="prebuilt-catalogs">Prebuilt catalogs</h2> <p>The <code>--prebuilt</code> flag loads a bundled tool catalog by name.</p> <p>Current bundled prebuilt:</p> <ul> <li><code>validation-runs</code></li> </ul> <p>Example:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./nocfoundry --prebuilt validation-runs </span></span></code></pre></div><p><code>--prebuilt</code> is not a boolean flag, and it does not take an individual tool name. This is invalid:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./nocfoundry --prebuilt start_validation_run </span></span></code></pre></div><p>because <code>start_validation_run</code> is a tool inside the <code>validation-runs</code> catalog, not the catalog name itself.</p>https://docs.nocfoundry.dev/dev/reference/faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.nocfoundry.dev/dev/reference/faq/<h1 id="faq">FAQ</h1> <h2 id="does-nocfoundry-execute-prompts-itself">Does NOCFoundry execute prompts itself?</h2> <p>No. Prompt resources are exposed for clients and agents to consume. NOCFoundry does not execute prompts against an LLM.</p> <h2 id="why-is-api-returning-401">Why is <code>/api</code> returning 401?</h2> <p>If endpoint auth is enabled, callers must present a bearer token that matches the configured <code>/api</code> audience.</p> <h2 id="does-the-ui-require-login">Does the UI require login?</h2> <p>The UI shell can remain public while its backing <code>/api</code> calls are protected. When UI auth is enabled, the browser signs in through OIDC + PKCE.</p>