Foixar for Visual Studio Code

Turn approved requirements into governed, reviewable implementation without leaving your editor.

Foixar connects the code in your active workspace to an approved feature, its repository intelligence, organizational decisions, and governance rules. It plans the implementation first, shows the specialist-agent review as it runs, and presents generated changes as native VS Code diffs before anything is written locally.

Foixar · Platform · Security · Privacy · Support

An active Foixar tenant and a repository connected through the Foixar portal are required.

From requirement to reviewed code

1. Start from governed work

   Foixar binds the active repository, feature branch, commit, approved spec, plan, tasks, and current Repository Intelligence Revision. It will not generate against an unrelated branch or stale repository snapshot.

2. Review the implementation plan

   Select Foixar: Generate Implementation. The plan opens beside your code with expected file changes, implementation steps, risks, validation commands, and the Architecture Agent decision. Modify or approve it before generation begins.

3. Follow the live pipeline

   The right-side panel shows the same governed stages visible in Foixar Feature Studio: tenant-resource resolution, repository context, architecture review, stack specialists, security, tests, integration, deterministic validators, and preview preparation.

4. Inspect native diffs

   Generated files remain in a controlled preview. Review each proposed change using VS Code's side-by-side diff editor. Foixar explains why each file is present and carries forward agent findings and validation evidence.

5. Accept or reject explicitly

   Accept All applies the approved files as uncommitted workspace changes. Reject records the decision and leaves the workspace untouched. Nothing is committed or pushed during acceptance.

6. Validate in the repository

   Run the allowlisted lint, build, and test commands detected from repository intelligence. Bounded results are attached to the implementation audit record. If repository dependencies are missing, Foixar can show the exact deterministic install command, ask for approval, and retry validation. It never installs dependencies or changes generated files silently.

7. Commit and publish explicitly

   Finish implementation first shows the exact validated paths and commit message. Foixar stages only those paths and runs normal Git hooks. Foixar itself does not invoke git push during this gate, although repository-controlled hooks can have their own side effects. A separate Push & Finish confirmation then conditionally publishes that exact commit only while the remote remains at the SHA Foixar inspected, verifies the resulting remote SHA, and links the published commit to the audit trail. If a hook already published the exact reviewed commit, Foixar detects and verifies it before reconciliation. It never force-overwrites remote work. You can cancel either gate and continue through Source Control instead.

What you get in VS Code

My Work

See the governed feature attached to the current branch as an ordered workflow: repository and branch, Repository Intelligence, requirement approvals, slice/fingerprint context, implementation review, validation, and publication. Requirements 3/3 approved is shown separately from repository readiness so an approved feature is never mistaken for a fully ready workspace.

When Repository Intelligence is the current blocker, Refresh Repository Intelligence runs the same tenant-scoped recon, App Profile, and code-index pipeline used by the Foixar platform. VS Code follows an existing active run instead of duplicating it, reports scan and indexing progress, then automatically checks the next prerequisite. Recreating a feature branch does not by itself require another repository scan.

Governed implementation

• Persistent right-side implementation plan and live pipeline
• Independent Architecture, Security, Test, and Integration Agent reviews
• Versioned plan modification and approval
• Generated-change preview with per-file rationale
• Native side-by-side diffs
• Explicit accept or reject control
• Local apply with rollback if a filesystem operation fails
• Repository-native build and test evidence

Spec Context

Open the approved specification, implementation plan, delivery tasks, and data model for the current feature as read-only virtual documents. The sidebar shows their friendly names and source filenames, and identifies artifacts that have not been generated yet. Foixar does not copy these artifacts into the working tree.

Local validation and recovery

• Repository-native commands run without a shell, using resolved absolute executable paths and bounded, redacted output.
• Before any check runs, Foixar verifies required tools, declared engine versions, installed dependencies, and package-manager/lockfile consistency.
• Runtime findings are classified as Environment missing tool, Environment wrong version, Dependency missing, Command failed, or Repository misconfiguration.
• Missing Node dependencies are treated as workspace setup, not as a generated-code defect. Foixar can propose the lockfile-aware install command, request explicit approval, and automatically retry validation.
• Missing machine-level tools remain under developer or workstation-administrator control. Foixar shows every path it checked and can open a file picker to save an explicit executable path.
• Lint, build, or test failures show their command output and workspace diff so the developer can diagnose the proposed implementation.
• Foixar never rewrites accepted files silently. A repair is generated as a separate bounded proposal, shown as a native diff, and applied only after explicit approval.
• Every rerun starts with an empty result set and is bound to the repository, branch, HEAD, workspace diff, resolved tools, command set, and validation-attempt number. A delayed result from an older run cannot replace the latest evidence.
• The panel identifies whether a result came from the current execution or restored audit evidence. Clear Validation State removes stale or unwanted evidence without changing generated files or resetting attempt history.
• After repository checks pass, the native Validated Files view lists each created, updated, or deleted file, its check status, and actions to reopen the native diff or file. Run Foixar: Show Validated Generated Files at any time to reveal it. To keep it on the right, right-click the Validated Files title, choose Move View, then Secondary Side Bar; VS Code preserves that placement.
• The validation report body scrolls independently beneath a fixed action dock, so the active check, live progress, Run/Cancel, and review controls remain visible throughout long output.
• Copy Diagnostics produces a privacy-safe runtime report; detailed execution logs are available in the Foixar Validation output channel.

PR governance

• Pull the latest Foixar governance review for the active branch
• See line-anchored findings in the editor gutter
• Inspect blocker, warning, and informational evidence on hover
• Open the associated pull request from the finding
• Track current blocker and warning counts in the status bar

@foixar chat

Ask about the current branch's approved artifacts or latest governance findings from VS Code Chat:

• @foixar /spec
• @foixar /plan
• @foixar /tasks
• @foixar /explain

Safety boundaries

Foixar is designed to preserve developer control:

• It does not switch branches.
• It synchronizes a governed branch only by clean-worktree fast-forward; local-ahead, diverged, or deleted remote branches require an explicit human decision.
• It does not write over a dirty worktree.
• It does not reuse approval after the branch, remote, commit, or repository-intelligence revision changes.
• It does not apply files outside the approved manifest.
• It never commits or pushes silently. Finish implementation requires a visible commit approval and a separate push approval.
• It stages only the validated generated-file manifest, rejects unrelated workspace or committed paths, binds Git blobs to the exact validated bytes, runs normal Git hooks, never force-overwrites remote work, and verifies the remote SHA before reconciliation.
• It does not write bearer tokens to repository files or VS Code settings.
• It stores the short-lived access token and rotating refresh token in VS Code SecretStorage.
• An explicitly exported CLI access token is short-lived, written outside the repository with restricted permissions, and never includes the refresh credential.
• Foixar API keys are reserved for CI, service automation, and external integrations; they are not the developer sign-in mechanism.
• Tenant and repository authorization are enforced by the Foixar API, not trusted to the extension UI.

Before you install

You need:

• VS Code 1.90 or later
• Git and the built-in VS Code Git extension
• An active Foixar tenant
• A repository connected in Foixar with Repository Intelligence Ready status
• An approved Foixar feature attached to the branch you have checked out

Foixar 0.7 supports governed feature-branch workflows on connected source-control providers, including Azure DevOps and GitHub. Repository and branch identity are verified again before planning, preview generation, and local apply.

Get started

1. Install Foixar from the Visual Studio Marketplace.
2. Open the repository that is connected to your Foixar tenant.
3. Check out the exact feature branch shown in Foixar Feature Studio.
4. Open the Foixar activity-bar view.
5. Select Sign in to Foixar. Your browser opens the Foixar portal for Microsoft or Enterprise SSO and returns you to VS Code after approval.
6. Open My Work and run Check Implementation Readiness.
7. Select Generate Implementation.

Feature Studio can also open the exact pushed feature directly in VS Code. The handoff contains only non-secret feature, Application-binding, repository, and branch hints; the extension resolves the configured Foixar environment and verifies every identity against the active workspace before planning.

Business users may instead start hosted generation in Feature Studio. That option still writes only to the governed feature branch and does not bypass architecture validation, pull-request review, or merge controls.

For development environments, set foixar.apiBase to the API endpoint supplied by your Foixar administrator. Customer installations use the live endpoint by default.

Commands

Settings

How Foixar resolves validation tools

For every required tool, Foixar resolves one executable deterministically:

1. The matching explicit foixar.*Path setting.
2. A workspace-local executable, including node_modules/.bin.
3. The VS Code extension host's PATH.
4. Known platform locations for macOS, Windows, and Linux, including common version-manager directories.

An explicit workspace override remains authoritative. Without one, Foixar compares discovered Node versions with every recognized engines.node range in the repository and selects the first compatible installation. On macOS and Linux, Foixar discovers side-by-side installs from nvm, fnm, Volta, asdf, mise, and versioned Homebrew formulas. On Windows, it discovers nvm-windows, fnm, Volta, and mise installs; asdf installations inside WSL are discovered when the repository is opened in a WSL extension host, where they are Linux executables.

Foixar records each tool's source, absolute path, and version, then runs it with shell: false. npm, pnpm, and Yarn are paired with the selected Node installation when possible; their version probes and child processes use that same Node without changing the workstation PATH. Foixar never silently installs a global tool or changes a workstation setting. A manually selected executable is kept in VS Code's private workspace storage for that repository; Foixar does not write the path into .vscode/settings.json.

For JavaScript repositories, the packageManager field is authoritative. When it is absent, Foixar uses the repository lockfile; without either, it defaults to npm. npm, pnpm, Yarn, and Bun are supported. Conflicting lockfiles or a mismatch between packageManager and the lockfile block validation instead of being guessed through.

Validation runtime troubleshooting

Executable not found (ENOENT)

1. Open Foixar Local Validation and review Environment Preflight.
2. Expand Paths Foixar checked to confirm which executable locations were inspected.
3. Select Choose executable and point Foixar to the tool already installed on the workstation, or install the tool using the platform's normal managed process.
4. Select Recheck Environment and Continue. Foixar reruns preflight first and resumes repository checks only after it passes.

Typical installation sources are the official Node.js installer or a managed version manager on macOS/Windows/Linux, Corepack for pnpm or Yarn, the official Bun installer, and the official .NET SDK installer. Foixar presents OS-specific guidance but does not execute a global installation.

Engine version mismatch

Foixar compares the resolved versions with package.json engines and the declared package-manager version. Select a compatible executable from Environment Preflight or change versions through the team's normal version manager, then rerun preflight. Repository engine declarations are not weakened automatically.

Dependencies missing

Foixar offers the deterministic repository-local restore (npm ci, frozen pnpm/Yarn/Bun install, or an explicitly disclosed install that may create a lockfile). The command is shown before execution and runs only after approval. After a successful restore, Foixar reruns the failed preflight checks before continuing validation.

A previous failure is still visible

Start Run Again to create a new validation attempt. The panel immediately removes the previous command results and shows only events from the new attempt. If persisted evidence itself should be discarded, select Clear Validation State. The clear is tenant- and user-scoped, audited by Foixar, and never modifies the working tree.

Support and privacy

Foixar does not include customer model credentials in the extension package. Tenant model and storage resources remain configured through the Foixar portal.

• Contact Foixar support
• Security practices
• Privacy policy
• Terms of service