Local runtime
.agent stays authoritative
Execution traces, status, and repo context remain close to the work instead of becoming a black box.
Local-first operating layer
Keep AI execution close to the repo.
Veloran gives autonomous coding work a durable operating model: repo-native execution stays local, the Hub receives only structured state, and every run leaves behind a Resume Bundle the next person can actually use.
Local-first source stays authoritativeStructured Hub progress stays reviewableResume Bundle handoffs stay short
Real repo loop
Repo-native state
.agent/execplans/launch.mdin_progress
.agent/runs/current/status.jsontruthful
packages/core/src/local-state/scanned
Resume Bundle
Goal
Stabilize the launch branch and ship the public site.
Evidence
Landing shipped, app entry live, auth verified.
Next
Open the dashboard, review the pack choice, continue the repo loop.
Hub state
Readable
Artifacts
Structured
Assistants
Portable
Hosted hub
Only structured state syncs
Milestones, blockers, decisions, artifacts, and summaries stay available without mirroring raw source by default.
Resume flow
Later sessions inherit context cleanly
Resume Bundles turn a messy handoff into a short operational state that another assistant or teammate can pick up.
Compatibility
Codex, Claude, MCP, packs
Veloran does not force one assistant worldview onto the repo. It keeps the workflow legible across tools.
The product loop teams actually need
The public story is simple because the loop is simple: start from the repo, keep execution local, sync just enough structure to inspect progress, then resume from a clean handoff instead of a giant context reload.
Start from the repo you already have
Veloran keeps execution grounded in the working tree, not in a detached cloud abstraction. The repo remains the source of truth.
Sync only the structured parts that matter
Progress, artifacts, blockers, milestones, and decisions move into the Hub so teams can inspect AI work without rereading the entire codebase.
Pick the work back up without losing the plot
Resume Bundles compress the current situation into a handoff-ready state: what changed, what is blocked, what evidence exists, and what to do next.
What stays local and what gets shared
Veloran is designed for teams who want more visibility without handing the entire repo over to a hosted control plane.
Stays in the repo
Execution context remains local-first
Plans, run traces, temporary artifacts, and repo-native status under
.agent.Source code and live edits stay close to the machine doing the work.
Assistant prompts and repo-specific execution details do not need to become hosted state by default.
Syncs to the Hub
Only the structured review layer goes hosted
Milestones, blockers, recent evidence, project decisions, and pack choices.
Dashboard summaries that humans can inspect without opening local run files by hand.
Resume Bundles that preserve the current goal, evidence, and next action for the next operator.
Built for the toolchain you already use
The current MVP already ships the CLI scaffold, Hub API, dashboard, pack system, and MCP surface. The public site should feel just as real as the working product underneath it.
Assistants
Codex and Claude ready
The product surface is already paired with the existing pack system, CLI, and Hub API so the same project can move between assistants.
Control plane
MCP and API friendly
The hosted boundary exposes structured project state instead of raw repo files, which keeps integrations auditable and deliberate.
Workflow
Built for real repository loops
Scaffold, sync, inspect, repair, and resume are not slides in a concept deck here. They are already functional paths in this repo.
Teams
Handoffs stay intact
Artifacts, decisions, and current milestones remain legible after the original operator has moved on to the next task.
Why teams can trust the loop
Veloran is not trying to be a magical AI veneer. It is trying to make the work legible enough that humans can ship, debug, review, and resume it without ceremony.
Execution
Local-first by default
Source, prompts, and repo state stay close to the machine doing the work. Veloran does not need to mirror your codebase to stay useful.
Visibility
Readable by humans, not just agents
The Hub turns autonomous work into dashboards, milestones, decisions, and evidence that people can actually review.
Portability
Switch assistants without resetting context
Codex, Claude, MCP clients, and packs can all move through the same loop because the durable state is structured and vendor-neutral.
Recovery
Resume without reloading the whole repo
Resume Bundles make the next session smaller, faster, and easier to validate because the current state is already summarized.
Go from interest to a working workspace in minutes.
The app surface is live right now. Create an account, step through onboarding, and move straight into the dashboard, packs, and project loop that already exist in this repo.