Inside Kashira

Stop reverse-engineering your own code. Kashira remembers why it’s the way it is.

Kashira auto-records decisions, tradeoffs, and mistakes—so you can ask about your codebase without reconstructing the past.

Free local workspace Vibe and Dev in one workspace
Inside Kashira

The coding workspace that remembers the whole project.

A solo developer can work with the continuity of a team—without re-explaining the codebase every time.

Review before apply Local model support Durable project memory Nearby team collaboration
Three defining systems

More than code generation. An engineering relationship.

Kashira combines the partner doing the work, the memory preserving its reason, and the nearby team moving it forward.

Permanent Engineer Memory

What you built. Why you built it. What went wrong.

Kashira preserves decisions, tradeoffs, mistakes, architecture, conventions, and important changes as durable project memory—automatically.

  • Preserve decisions and their rationale
  • Keep architecture, conventions, and incidents findable
  • Carry useful project context across sessions
See how project memory works
Project Memory
VIBEDEV
PERMANENT ENGINEER

Project Memory

Durable engineering notes Kashira carries across sessions: decisions, bugs, conventions, architecture, and important research.

OnAskOff

Prevent duplicate invite acceptance

BUG

Webhook retries could accept the same organization invite twice. Acceptance now uses the persisted invite event ID as its idempotency key and returns the existing membership on a repeat request.

Created Sep 21 at 14:15Updated Sep 21 at 14:15highactive2,184 memory tokens est.main @ 7cd841aserver/routes/invites.tsserver/services/memberships.tspnpm test invites
Open detailsClose details
DURABLE IMPLEMENTATION CONTEXT

The existing event ID is the durable boundary between delivery retries and membership creation. Do not introduce a second idempotency identifier unless the upstream event format changes.

Keep invite permissions server-authoritative

DECISION

The client may hide unavailable actions, but the API remains responsible for checking organization role, seat availability, and existing membership before an invite is created.

Created Sep 21 at 13:42Updated Sep 21 at 13:42highactive1,702 memory tokens est.main @ 81ac239server/policies/invites.tsapp/admin/invite-form.tsxpnpm test policies
Open detailsClose details
DURABLE IMPLEMENTATION CONTEXT

UI state is treated as guidance only. Authorization, capacity, and membership checks must run inside the invite transaction so alternate clients follow the same rules.

Project memory oninvite-delivery2 recent notes
Vibe / Dev mode

One app for two ways of working.

Stay in a clean, conversation-led workspace when you want momentum. Switch into the complete developer environment when you want direct control.

01 / VIBE MODE

Describe the outcome.

Maestro keeps the plan, activity, and conversation focused while the project continues underneath.

Conversation-led building Plans and progress stay visible The workspace stays out of the way
Recovery flow
Can you make the landing page feel like Kashira?
Worked for 18s

I aligned the page with the workspace: deep charcoal surfaces, purple active states, and calm neutral text.

  • Unified the header and hero
  • Removed perspective transforms
  • Added responsive workspace previews
Ask Kashira to build…
KashiraVIBE TERMINALv0.1.0
Northstar team room3 teammates · 3 paired agents
LIVE
SHARED TEAM CONTRACT
Ship organization invites3 teammates · 3 paired agents
TheoFrontend engineer · Human

The invite form is ready. I’m routing the API contract to Priya’s agent.

TK
Theo’s AgentFrontend · Theo
Contract · API route

@backend-agent Add POST /organizations/:id/invites. The form expects inviteId, email, and status.

PS
Priya’s AgentBackend · Priya

Route added on the shared branch. Duplicate email handling matches the contract.

LA
Lina’s AgentReviewer · Lina

Route and form reviewed together. Validation and keyboard flow pass.

Team contract ready for review
Message teammates and their agents…
Available in project rooms
Realtime Role Agents Collaboration

Your agent works with mine. Our team stays connected.

Each teammate brings one role agent into a shared project room. Agents route work between frontend, backend, and review while people remain responsible for decisions.

Local or cloud Use a nearby WLAN room or a signed-in Kashira Cloud room.
Explore
The complete product

Nine capabilities. No invented promises.

Every capability listed here is integrated into Kashira today, with future availability called out explicitly.

Local. Kashira Cloud.

Choose where the intelligence comes from.

Model choice is a boundary you control, not a decision hidden behind the interface.

LOCAL

Local models

Run compatible models on your machine. Choose the model and hardware that fit your project, with local control over inference.

CLOUD

Kashira Cloud

Use managed cloud access with plan-based allowances and less provider setup.

Launch pricing

Start local. Add power when the work asks for it.

Four clear levels—from Free to Max—scale monthly credits, active context, model access, and concurrent cloud tasks.

Kashira plan system Four levels of access
01
Free
$0per month

Explore Kashira with capable economy coding models.

Plan access
  • 250 AI credits monthly
  • 200k active context
  • Economy models
  • Minimal feature access
  • 1 concurrent task
Get started
02
Plus
$15per month

For individual developers using Kashira regularly.

Plan access
  • 5,000 AI credits monthly
  • Full model context
  • Full cloud model catalog
  • Full feature access
  • 2 concurrent cloud tasks
Choose Plus
04
Max
$60per month

For intensive agentic coding and large projects.

Plan access
  • 30,000 AI credits monthly
  • Full model context
  • Full cloud model catalog
  • Full feature access
  • 8 concurrent cloud tasks
Choose Max
Choose your level

Free provides minimal feature access. Paid plans unlock the full Kashira feature set and progressively higher cloud capacity.

FAQ

A few useful answers.

Read the documentation →
What is the difference between Vibe and Dev?

Vibe puts the conversation and task progress first. Dev gives you direct access to the editor, files, terminal, and Git. Both work with the same project.

How do teammates and their agents collaborate?

Each teammate brings their own agent into a shared room. Frontend, backend, and QA agents exchange tasks and results while their human owners clarify decisions and review the work. Collaborate nearby over the local network or remotely through a signed-in Kashira Cloud room.

What does Permanent Engineer remember?

Project decisions, their reasons, conventions, incidents, and important changes. You can inspect the project journal and keep useful context across sessions.

How do local models and Kashira Cloud differ?

Local models run through a compatible engine on your computer. Kashira Cloud provides managed model access using your plan’s credit allowance. Local performance depends on the model and your hardware.

What changes between plans?

Free, Plus, Pro, and Max offer different monthly credits, active context limits, model access, and concurrent cloud-task capacity. Compare the current allowances on the pricing page.

Where can I find the right desktop build?

The download page lists release information and available builds. Check the platform and system requirements before installing.

Keep the thread

Your codebase deserves an engineer that remembers.

Start with the free local workspace. Bring Maestro, Permanent Engineer, and your preferred model path when you are ready.