NetworkBase

Keep project files, tasks and reviewed changes close to your editor.

Work loop

1. Connect your NetworkBase account from the sidebar. Browser sign-in uses a one-time authorization code; manual device-token entry is also available. Credentials stay in IDE SecretStorage.
2. Choose a project. Browse cloud files on demand, use My tasks / All tasks, and inspect task descriptions, properties, subtasks and linked files.
3. Open a file in the native editor. Saving writes a local saved generation. It does not publish a revision or change a task’s status.
4. In Changes, select saved files, inspect differences and choose the revision policy, task-file effects and optional note. No files are selected automatically.
5. Review the exact saved snapshot and confirm publication. Follow real transferred bytes, finalized file receipts and separate task updates. Operations retains partial and uncertain results for reconciliation.
6. Run an existing configured IDE check when needed. Choose specific check reports and published revisions for an evidence packet, then explicitly complete the task or submit it for review according to the project’s completion setting. By default review is off. Project owners and co-leaders can require review in Project settings → Lifecycle & Workflow. Pending reviews still need approval or requested changes after the setting is switched off. Changed requirements, subtasks or deliverables must be resubmitted before approval. File publication remains separate.

The slim sidebar uses NetworkBase typography, project images, section dividers, aligned tabs, accessible controls, loading states and a name-only account footer. Task cards and detail views have one top-level route to the full task in the application.

Native IDE features

Use NetworkBase: Workspace Actions or the Command Palette for:

• Task context, task detail in an editor, and creating a task from selected code after confirmation.
• Project filename search, cached-content search, and explicit bounded server-content search.
• Native file diffs, version history, incoming comparison and local conflict resolution.
• Recovery comparison/restoration, operations history and an inspectable redacted support bundle.
• Optional Source Control integration, backed by the same saved changes and review command.
• Explicit local-folder mapping and manually selected saved-file staging. Linking never uploads a folder, clones a repository or changes Git.
• Existing configured IDE tasks, native terminal output, cancellation and fingerprinted check reports.
• Revision-anchored native comments with authorized replies, resolve/reopen and explicit relocation.
• Bounded AI context preparation. Optional chat and read tools are registered only when the IDE exposes their APIs; manual inspection/copy remains available.

AI/repository text cannot authorize execution, task mutation or publication. This release does not enable autonomous AI mutation tools.

Publication and recovery

A review freezes file bytes, baselines, project, revision policy, note and captured task associations. A newer saved generation invalidates a fresh review. Dirty editor buffers are never automatically saved during publication.

Publication is per file. A byte upload is not a finalized revision. Completed files remain recorded if a later file or task update fails. A timeout stays unknown until queried against durable server receipts. An explicit retry uses the original operation identities and sends only unconfirmed files; task-only retries upload no files.

Saved changes, recovery and operations are isolated by approved application origin, verified account and host. Window/workspace branches retain separate saved generations, and project publication has an exclusive owner. Disconnect retains local work. Ambiguous legacy data is held for explicit import, with originals retained; importing cannot overwrite a different local draft.

Recovery text can be compared or restored as an unsaved editor edit. Binary/large recovery opens in a read-only native viewer. Staging recovery creates local work that still needs selection and publication review. Local recovery is best effort; no product can guarantee recovery after every disk or operating-system failure.

Settings

Credentials, environment/key files, symlinks and paths outside the mapped root remain excluded from manual local staging. Inspect inclusion rules before staging. Server restrictions cannot be bypassed by changing these settings.

Compatibility and limits

• Desktop/Node extension hosts and remote Node workspaces are the implementation targets. Minimum manifest version: VS Code 1.75. Optional newer chat/LM APIs are feature-detected.
• This package has no browser extension-host bundle. Browser-only execution is unsupported.
• Workspace Trust gates remote writes, local-folder staging, checks and comment posting. Read and retained recovery remain available within the declared limited mode.
• Protocol 2 requires the matching NetworkBase application/backend changes included with this release. Normal application deployment must include the migration journal and 0220_extension_operation_receipts_index.sql.
• Project pages: 25; task pages: up to 100; filename/folder pages are cursor based. Native Explorer reads at most 5,000 entries in one folder and explains how to narrow larger folders.
• Manual local scans: 200 candidates. One review: 100 files. Native current-file transfer/view: 100 MiB, subject to server limits. Inline uploads: 512 KiB; larger uploads use signed storage/finalization.
• Native historical bytes: 2 MiB per revision, with larger history handed off to the application. Binary historical bytes within the limit use a read-only native viewer.
• Server-content search explicitly scans up to 20 eligible text files per page, each at most 64 KiB. Cached search searches only retained bytes; it does not silently download a project.
• Comment inspection is capped at 2,000 events; narrow to a specific thread when needed. AI context is bounded to 64 KB.

No source/credential analytics or automatic support upload is sent. The support bundle is inspectable before copying.

Verification

Run npm run test:code, npm run lint, and npm run package. These are code-only checks and do not launch an IDE or browser. The production acceptance mapping and deployment notes are in docs/production-implementation.md.

NetworkBase · Repository