FIELD GUIDE / COMMON QUESTIONS
Clear answers.
Room to grow.
Veasel Code is being built in public. Here is what the current source build does, what it does not do yet, and where to follow changes.
Can Veasel Code edit my repository?
Not yet. The current build can keep sessions and chat with a configured model. It cannot read files, apply patches, or run shell commands.
Does my code stay on my machine?
Session history is stored locally. Prompts and recent conversation context are sent to the model provider you configure. The current product does not attach repository files because repository tools are not implemented.
Which AI providers can I use?
The V backend has synchronous adapters for OpenAI-compatible APIs, Anthropic, and Gemini. See provider setup and data disclosure details.
Can I use Agent Plugins already?
No. Package, Skill, and MCP configuration validation is experimental. Veasel cannot install plugins, run MCP servers, activate Skills in model turns, or manage plugin approvals yet.
Why is the terminal client TypeScript?
The TUI uses OpenTUI for terminal rendering and talks to a versioned API. The server, agent runtime, and persistence are V; the client remains a separate API consumer.
Can I use the Veasel mascot commercially?
The official mascot and this pixel adaptation are under CC BY-NC 4.0. Commercial use needs separate permission from the rights holder.
How do I follow the project or contribute?
Read the verified roadmap, open the repository, and use its issue or pull request templates to propose focused work.