Historical project case snapshot: 2026-10-27. Current editor downloads are described in the release note below.
Own projects and application examples
These are projects of one author, not client references. For each case you see the task, the author's role, the current status, what was done, the result, a working link and the part that Tvijo actually plays. Where something is not verified, the case says so.
Three cases with a public track record
Each case links to the repository and to a live release page. The evidence dates are the ones recorded in the project receipts; where a receipt is missing, the line says “not verified”.
AI OS: an orchestration and audit layer for agents
- Task
- Keep several AI workers under control: one task per session, explicit paths a worker may write, a recorded model and session for each artifact, and a stop rule instead of an endless retry loop.
- Author's role
- Owner and author: architecture, agent policies, storage on the volume, publication rules for releases.
- Status
- Research repository; the public pages and client builds are served from the separate deployment volume.
- What was done
- Rules for shared worktrees and write allowlists; an improvement pipeline with a register of proposals; release publication rules (checksums, anonymous download verification, EN/RU changelog-to-download journey) recorded in a single journal.
- Result
- A workable discipline that shows up in this site's own release pages: versions are published with ranges and SHA-256, and what was not tested is stated.
- Tvijo's confirmed role
- The orchestration rules behind the Tvijo releases and these pages. Not a commercial Tvijo product until the licensing decision is published.
DSHREM: one service across browser, editor and terminal
- Task
- Give an AI developer loop a single account and service, reachable from a web workspace, from VS Code (locally or over Remote SSH) and from the command line, without scattering API keys across machines.
- Author's role
- Author of the extension, the terminal client and the data rule that decides what leaves the machine.
- Status
- GitHub preview: checksum-verified VSIX 0.10.17 published 2026-10-27; Marketplace publication deferred.
- What was done
- Extension for VS Code and VSCodium with agent tools behind confirmations and Full access only by explicit approval; native symbols, definitions and references; a bundled offline Russian learning guide; terminal client (Node 22+,
dsh) with sessions, a local knowledge base, JSON output and a documented privacy rule: nothing is scanned automatically, only what you select or attach is sent. - Result
- Three surfaces work with the same account and the same task model; the editor can run against a remote project without the code travelling to a laptop.
- Tvijo's confirmed role
- This is the product Tvijo ships; the public source preview and the download page are linked below.
Tvijo Code: a portable Windows editor with the agent built in
- Task
- Ship the editor loop as one application on Windows: TVIJO branding, DSHREM built in, and a matching Linux server for code that has to run on a project machine.
- Author's role
- Author of the build pipeline, the branding, the bundled extension and the release evidence.
- Status
- Preview release: portable ZIP for Windows 10/11 x64, unsigned; Linux x64 Remote SSH server published on the same tag.
- What was done
- Built from Code - OSS 1.140.0; 209.6 MB (219,805,882 bytes) ZIP verified anonymously with the published SHA-256; Windows CI run 40524272994 covered command-line launch, extension activation, the offline guide, symbols, definitions and references; all 71 embedded extension files match the published VSIX byte for byte.
- Result
- The whole loop (task, context, execution, check) in one window, with a verifiable download receipt.
- Tvijo's confirmed role
- The downloadable editor release carrying Tvijo branding and the DSHREM extension.
- Not verified
- Interactive sign-in, a paid model answer, a complete coding task on a user machine, a real Windows-to-Linux SSH session. Windows on ARM and 32-bit Windows are not supported.
What can be ordered today
Four services, each scoped per task instead of sold from a price list: you describe the task and the systems involved, and the reply is what is delivered, what is checked, what is out of scope and an estimate for that task. Commercial terms are not set, so no price or term is published on this page.
AI assistant for incoming requests
Answers from the company's own material, collects the details a request needs, and hands the complex cases to a human together with the context already gathered.
- Scope per task: the material it answers from, the fields it collects, and the rule for handing over to a person.
Telegram + CRM/API automation
Turns an incoming message into a record, a task and a notification, calling the systems the process already uses.
- Scope per task: which systems, which accesses, and a list of checks that has to pass before handover.
Voice AI assistant
Takes incoming calls, clarifies the request and prepares the summary of the conversation for the person who follows up.
- Pilot, not a shipped product: no service-level agreement, no published recognition accuracy, no call volume promised.
Web application development or rework
Builds a web application or extends an existing one: pages, forms, an admin view, or an API in front of data the owner already has.
- Scope per task: screens, data, who signs in, and what is explicitly left out of this round.
How to send a request
Name the service, the systems involved, the outcome you need and one contact. Write in the chat or by email; both reach the owner, and the owner replies with a scope.
Why there is no form on this page
The request receiver exists on the server, but every valid save today notifies the owner, there is no test mode, and the route does not store which service was chosen. Until that is closed, a form on this page would either lose the request or fire a notification on every test — so requests are taken through the chat and email above, and the page claims nothing else. Recorded on 2026-10-27.
How a task starts
- You describe the task and the systems involved, in one message or through the chat.
- You receive a scope: what is delivered, what is checked, what is out of scope, and the estimate for that task.
- Access is granted only for the agreed systems, and work starts after the scope is confirmed.
- Handover includes the check list and the result of each item, including the failures.
Editor preview released
Tvijo Code 1.140.07216 · DSHREM 0.10.28 · 2026-11-14. Windows x64, macOS Apple silicon/Intel, Linux x64. Not verified: sign-in, paid tasks, macOS notarization, Windows publisher trust. Linux package installers are not included.