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. Foixar never commits or pushes generated code for you.

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.

What you get in VS Code

My Work

See the governed feature attached to the current branch in four focused groups: the feature and active session, workspace binding, governed context, and any action required. Repository, branch, bound revision, Repository Intelligence status, approved artifacts, and implementation blockers stay visible without flattening everything into one list. Resume interrupted work without creating a duplicate run.

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 and with bounded, redacted output.
• 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.
• 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.

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 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 does not commit or push generated code.
• 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 the governed Azure DevOps feature-branch workflow. 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.

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

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