What works, what is next.

3 in development build · 2 planned

• Exit codes and timings per command

  Each command shows how long it took and whether it failed, so you can spot problems in a long session.

  In development build

• A terminal you can use all day

  Shells, tabs, split panes, search, themes and sessions that come back after a restart.

  In development build

• SSH in a tab

  Open a remote shell with the host's key checked first.

  In development build

• Remote files over SSH

  Browse, edit and transfer files on a remote machine from the same tab.

  Planned

• Windows shells tested by hand

  PowerShell, cmd and WSL checked on a real Windows machine, not only in automated builds.

  Planned

6 in development build · 3 planned

• Built-in code editor

  Open, edit and diff files next to the terminal. Saves never overwrite changes made outside Vekrun.

  In development build

• See what leaves your machine

  A preview of exactly what will be sent to a provider, before it is sent.

  In development build

• Use local models

  Ollama and LM Studio are detected on your machine and work offline.

  In development build

• Memory you control

  What an agent remembers is scoped to you, the project or a task, and you can see and delete it.

  In development build

• Coding sessions with Ask, Plan, Build, Debug and Review

  Every change is shown as a diff before it is applied. Commands run only with your approval.

  In development build

• Connect Claude, OpenAI, Gemini or any OpenAI-compatible service

  Add your own key, test the connection, and switch models per task.

  In development build

• Use coding-agent subscriptions you already have

  Sign in with an existing Claude Code, Codex or Gemini CLI account where a supported method exists.

  Planned

• Download local models from inside Vekrun

  Pick a model that fits your hardware and get it without leaving the app.

  Planned

• Diagnostics in the editor

  Errors and navigation from language servers while you edit.

  Planned

1 in progress · 1 planned

• Board with Start Work

  A Kanban of your tickets. Start Work opens a branch, a worktree and a terminal, or hands the ticket to an agent or an AI team.

  In progress

• Drag and drop, saved views and a team board

  Rearrange tickets, keep filters, and see your team's work next to your own.

  Planned

3 in development build · 1 in progress · 3 planned

• Ask several models to challenge a decision

  Independent takes, critique rounds and a summary that records where they disagreed.

  In development build

• One inbox for everything waiting on you

  Approvals, questions and reviews from every running agent, in priority order.

  In development build

• Turn an idea into a plan

  A structured plan with steps, files and acceptance criteria, which you approve before anything runs.

  In development build

• Delegate to a coordinated team

  A manager splits the work, agents build in separate branches, and a different agent verifies before you review.

  In progress

• Work that continues after you close the window

  Agent tasks keep running in the background and pick up where they left off after a restart.

  Planned

• Run agents on another machine

  Use a workstation or server you control for long tasks.

  Planned

• Scheduled and recurring tasks

  Run a workflow on a schedule or when something happens in your repository.

  Planned

2 in development build · 2 planned

• Compare findings from several models

  Run a review council on a contested change and see where the models agree and disagree.

  In development build

• AI review of your local changes

  Ask a model to look for problems in a branch or diff before you open a pull request.

  In development build

• Pull requests waiting for you

  Reviews requested from you and your teammates' pull requests, in one inbox.

  Planned

• Submit feedback to GitHub or GitLab

  Inline suggestions and review comments posted from Vekrun.

  Planned

3 planned

• Agents that use your other tools

  Connect Slack, Sentry, Notion, databases and more through MCP, with permissions per service.

  Planned

• Status updates sent back to your tracker

  When you deliver, the ticket moves and the pull request is linked, with your approval.

  Planned

• Connect Linear, Jira, Asana, GitHub or GitLab

  Your assigned tickets from every connected tracker, in one place.

  Planned

2 planned

• Signed installers for macOS, Windows and Linux

  Public builds with checksums and a working update path.

  Planned

• Guided first run

  Pick a shell and a theme, then connect AI or skip it.

  Planned