docs.velclaw.cfd

[zskbot]

Velclaw

AI-native software workspace for agents, developers, and teams.

Build, inspect, test, deploy, and operate software from one developer-focused workspace.

Get started · Architecture · Capabilities · Ecosystem · Development

---

What is Velclaw?

Velclaw is an AI-native software workspace focused on the full software lifecycle: agents, code, projects, builds, runtime, storage, services, review, and deployment.

The goal is to give coding agents and developers one coherent environment instead of forcing every workflow through disconnected tools.

Build software. Give agents context. Keep the workflow together.

Architecture

                         ┌─────────────────────────┐
                         │       AI AGENTS         │
                         │ models · tools · tasks  │
                         └────────────┬────────────┘
                                      │
                                      ▼
┌──────────────────┐       ┌─────────────────────────┐       ┌──────────────────┐
│ Projects & Files │ ◄──── │    VELCLAW WORKSPACE    │ ────► │ Build & Runtime  │
│ code · context   │       │ projects · code · state │       │ build · execute  │
└──────────────────┘       └────────────┬────────────┘       └──────────────────┘
                                        │
                         ┌──────────────┼──────────────┐
                         ▼              ▼              ▼
                    ┌─────────┐   ┌──────────┐   ┌─────────────┐
                    │ Storage │   │ GitHub   │   │ Deployment  │
                    │ data    │   │ review   │   │ delivery    │
                    └─────────┘   └──────────┘   └─────────────┘

Capabilities

Area	Purpose
AI Agents	Agent-driven development workflows and tool execution
Workspace	Projects, files, code, persistent context and state
Build	Build, validate and package software
Runtime	Execute workloads and development processes
Storage	Persist application data and files
GitHub	Repository integration, code review and delivery workflows
Deployment	Move validated software toward production
Developer UI	A single workspace for the software lifecycle

Product URLs

The public product surface uses velclaw.cfd as the canonical host. Product areas are path-based instead of separate product subdomains.

Product surface	Canonical URL
Velclaw	https://velclaw.cfd/
Velclaw Docs	https://velclaw.cfd/docs
VelclawHub	https://velclaw.cfd/velclawhub
VelclawHub Ecosystem	https://velclaw.cfd/hub
Velclaw Deploy	https://velclaw.cfd/deploy
Velclaw Skills	https://velclaw.cfd/skills
Velclaw Plugins	https://velclaw.cfd/plugins
Velclaw MCP	https://velclaw.cfd/mcp
Velclaw Tasks	https://velclaw.cfd/tasks
Velclaw Dashboard	https://velclaw.cfd/velclaw
Velclaw Repo	https://velclaw.cfd/repos/new
Velclaw API Keys	https://velclaw.cfd/api-keys

Infrastructure-generated hostnames are not product URLs.

Technology stack

Quick start

git clone https://github.com/Velclaw/Velclaw.git
cd Velclaw
npm install
npm run dev

Open http://localhost:3000.

Validation:

npm run type-check
npm run build

Project structure

Velclaw/
├── app/                 # Next.js application routes
├── components/          # UI and workspace components
├── lib/                 # application services and integrations
├── public/              # public assets
├── server/              # server-side runtime pieces
├── drizzle/             # database schema/migrations
├── .github/             # CI and automation
└── README.md

GitHub workflow

Issue / Task
     │
     ▼
Agent + Developer
     │
     ▼
Workspace → Code → Build → Typecheck
     │
     ▼
GitHub branch
     │
     ▼
Pull Request → Review → Merge
     │
     ▼
Deployment

Technology ecosystem

These are open-source ecosystem references, tooling, inspiration, or attribution links. They are not presented as sponsors unless a separate sponsorship relationship is formally established.

Core ecosystem

• Vercel
• Next.js
• tsx
• Tenderdash
• Dash Platform

Icons, assets and developer tooling

• Simple Icons
• VectorLogoZone
• thesvg
• developer-icons
• vscode-icons-svg
• profile-readme-generator
• GitAscii
• GitHub Profile README Generator

Credits and attribution

Velclaw references open-source software and community tooling. Each external project remains the property of its respective authors and maintainers; applicable licenses and attribution requirements should be preserved.

Documentation

• Velclaw repository
• Issues
• Pull requests
• Official documentation: https://velclaw.cfd/docs

Contributing

1. Create a branch.
2. Make the smallest coherent change.
3. Run typecheck/build where applicable.
4. Open a pull request.
5. Address review feedback.
6. Merge after required checks pass.

Security

Do not commit credentials, API keys, OAuth secrets, database URLs or private deployment tokens.

Roadmap

The roadmap should reflect shipped work rather than fictional dates or commitments.

• Core workspace
• GitHub integration foundation
• Build/runtime workflow foundation
• Expand agent workflows
• Expand deployment automation
• Production-grade observability
• Broader ecosystem integrations

License

The current project configuration identifies Velclaw as private software. Do not claim an open-source license until a LICENSE file and public licensing decision are present.

Visual identity

The repository includes the official Velclaw mark and a lightweight product-introduction GIF so the project identity remains visible throughout the README rather than only in the hero.

---

Velclaw
Code. Innovate. Elevate.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.

[zskbot]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.