Skip to main content

Developer tools · Private preview

Ellygent for VS Code

Find the requirement, see why it exists, and follow its test links without leaving your editor.

This page describes preview v0.4.5. The extension is not on the Marketplace, and there is no public download yet.

Open your first requirement

These instructions are for testers who already have the private VSIX package. You can read this guide without an account.

  1. Install the preview. In desktop VS Code, open Extensions → … → Install from VSIX… and choose the package you were given. Reload the window if prompted.
  2. Open Engineering Context. Click the Ellygent icon in the Activity Bar, then choose Open Offline Sample. No account, CLI or network connection is needed.
  3. Follow the evidence. Open the planter requirement about speed changes. Read the rationale and recorded links, then try Review Desk or compare the two sample baselines.
Actual VS Code welcome sidebar showing Open Offline Sample, public browsing and private PAT connection
Captured in preview v0.4.1. The offline sample remains the main action; public browsing appears when examples are available.
Fictional planter requirement in VS Code with its B1 baseline, rationale and two recorded links
Actual preview v0.4.1, using the fictional planter baseline. Recorded behavior, rationale and links appear together. In v0.4.5, Copy review draft replaces Copy context.

Browse a public snapshot: choose Browse Public Projects or run Ellygent: Open Public Project Link. When the gallery is enabled and has published snapshots, you can read their approved documents and search without a token. If the gallery is empty or unavailable, use the offline sample.

Connect to a private project

Private online access in this preview uses Ellygent CLI 0.1.3 or 0.1.4 and a read-only personal access token (PAT).

  1. Install the supported CLI using the CLI installation guide. Open a local folder you control. If VS Code asks, trust only that folder, not a parent with unrelated files.
  2. In Ellygent, open Account → Personal Access Tokens → New Token. If asked, complete identity verification. Create a short-lived context:read token.
  3. In VS Code, choose Connect with a PAT. Select your trusted CLI executable and paste the token into the masked prompt only. Use it for this session or explicitly choose to remember it in VS Code’s encrypted secret storage.
  4. Expand Organization → Project and select Live or a named baseline. Choose a local operating folder. Live is a point-in-time pull; a named baseline stays pinned. The sidebar shows the active project, version and folder.

Only one project is active at a time. Closing it keeps the project tree available. Disconnect and Forget PAT clears the extension’s local connection; revoke the key in Ellygent to disable it on the server. Local exports are not deleted.

Available in the private preview

Find and navigate

Browse specifications and their engineering hierarchy by title. Search the active export by title, category, content or identifier.

Trace and compare

Read rationale and recorded relationships, and compare named baselines from the same project. Missing export data does not prove a missing test link.

Review Desk and review drafts

Work through questions about system behavior, inspect text and link changes, and preview a handoff before copying it. Copy review draft includes the selected item and its version; recorded link IDs are optional and linked item bodies are excluded. Draft proposals stay local and are not submitted or approved.

Work with local context

Open an extracted CLI context folder containing .ellygent/manifest.json. Private pulls create a new subfolder in your chosen directory. Refresh is explicit, not background sync.

Referenced files

For a connected private project, Refresh Baseline via CLI can also bundle available files referenced by the selected version’s Markdown. Referenced files lists new, changed and unavailable files. Named baselines pin document text; current server files are not verified historical evidence. External references are reported without fetching them.

Support and troubleshooting

Platforms

The preview is for desktop VS Code (1.92 or newer). Local Linux and macOS are the intended platforms for online private access. Windows and remote workspaces are not supported for that flow in this preview. You can open an already-extracted local export.

Where is the icon?

Check that the VSIX is installed in the current VS Code profile, then run Developer: Reload Window. Run Ellygent: Getting Started to reopen the walkthrough.

CLI or token error

Confirm that the selected executable is CLI 0.1.3 or 0.1.4. Check that your token hasn’t expired or been revoked, and that the account can access the project. Never paste a token into chat, settings, source code or a ticket.

Keep exports private

Choose a folder outside version control for private context, or exclude the generated export folder. Review excerpts before copying them into other tools. The extension doesn’t send them automatically.

Planned, not available now

Public distribution and a Marketplace listing will follow preview validation. Broader platform testing and a simpler setup are next areas to evaluate. This preview does not edit live projects, provide public snapshot downloads, or automatically send data to AI tools.

Share feedback on the preview
Ellygent

Define the system.
Build on shared understanding.

© 2026 Ellygent