Skip to content
Arctite

Context your AI can actually understand.Control you can actually see.

Arctite observes approved development sources, assembles relevant context locally, and turns that context into reviewable Guides and approval-gated execution.

Request AccessExplore Security

One workspace, many projects.

Every local project keeps its own context, its own intents, and its own permission set. One engine runs them all - nothing is mixed between projects.

WORKSPACE · LOCAL PROJECTS

engine running

aurora-projectfeature/auth

Fix authentication race condition

READY

vanta-coremain

Migrate session store to prepared statements

GATHERING

atelier-webfeat/onboarding

Add signup flow error states

DRAFT

One local engine · one intent active per project · context per project, never mixed

Intents, not open-ended prompts.

An intent states what you want to change. It moves through a visible lifecycle - created, drafted, ready, frozen - and freshness is tracked so stale context never quietly sneaks into a package.

INTENT INBOX

one active intent per project

Fix authentication race condition

#142 · active · 2 min ago

READY · 86%

Add retry backoff to session refresh

#141 · queued · 18 min ago

DRAFT

Replace fetch with streamed parser

#138 · stale · 2 days ago

REFRESH NEEDED
created → drafted → readyfreshness trackedrefine anytime

The Context Engine works only with what you approve.

Approved sources are assembled locally, scored against the active intent, and redacted before anything is shown to a provider. No enabled source, no data.

CONTEXT ENGINE · LOCAL

approved sources only

FilesGitTerminalBrowserClipboardNotes

Relevance

ranked by intent

Scope

project only

Redaction

before submission

Nothing is sent from this stage - assembly, scoring, and redaction stay on your machine.

Context Preview: the exact outgoing payload.

Every item is listed - files, Git state, terminal output, browser context. Remove items, watch the token count move, confirm redactions, and freeze the package to a digest before selecting a provider.

CONTEXT PACKAGE

FROZEN17 items4,810 tokens2 redactions

Files

├─ src/auth.ts · 1.1 KB├─ src/session.ts · 1.2 KB└─ + 15 more items

Git

├─ branch: feature/auth└─ diff: 41 additions · 17 deletions

Terminal

└─ npm test → 2 failures before fix

Browser

└─ 3 tabs · auth pages only
ProviderAnthropic
ModelClaude
Digest7e3b0f…a91c
Redactions2 secrets removed

This exact package, and nothing else, is what gets sent.

Frozen 23:14:08 · sha 7e3b0f…a91c

Guides: an editable implementation path.

Each approved package becomes a Markdown guide you can edit - diagnosis, affected files, implementation steps, verification commands, and a known rollback path. History stays local.

GUIDE · aurora-project

LOCALVALIDATED

INTENT #142 · 2 min ago

Fix authentication race condition

Diagnosis

Session lookup races with token refresh on startup. Two concurrent getSession() calls resolve against stale storage before the refresh settles.

Affected files

  • src/auth/session.ts
  • src/api/auth.ts

Implementation

src/auth/session.ts+1 · −1
1import { validatedSession } from "./validate"
2 
3export async function getSession() {
4- session = await getSession()
5+ const session = await validatedSession()
6 return session
7}

Wrap refresh in a single-flight promise so concurrent reads wait for the same settling token.

Verification

npm run verify -- auth
expect: 0 failures

Rollback

The package digest is frozen at approval. Restore returns to a known context package - no file writes happen without approval.

diff +14 −7 · verified locally

Agent Cycles execute one action at a time.

The provider returns a plan. Arctite validates it locally against project permissions, exposes typed actions, and waits for your explicit approval before each one. No arbitrary shell, no silent retries.

AGENT CYCLE

  1. Assemble context
  2. Review frozen package
  3. Write src/session.tsawaiting approval
  4. Run verification

Proposed write

+14 −7

src/session.ts

Type “approve” to execute this step

Recovery: return to a known package.

Every approved package is frozen to a digest before it is sent. When a run fails, inspect the before/after snapshot, restore, and resolve - with evidence of what was approved.

RECOVERY · SESSION SNAPSHOTS

LOCAL

Provider authentication failed.

Your context package was not sent. Nothing left the machine.

TimePackageTokensDigestStatus
23:14:08auth-race-fixpkg #1424,8107e3b0f…a91cverified
23:12:47auth-race-fixpkg #1394,69292c1f4…d4f7frozen
23:09:12auth-race-fixpkg #1315,032b0e4a3…3f2afrozen

Every approved package is frozen to a digest before it is sent. Restoring returns the workspace to a known context package - no file writes without approval.

Activity: a local trail of everything.

Context events, redactions, guide edits, approvals, and Agent Cycle actions are recorded in an append-only local ledger. What happened, when, and what it touched.

ACTIVITY · TODAY

local ledger · append-only

  1. 23:10:31

    Intent created

    “Fix authentication race condition” · feature/auth

  2. 23:11:02

    Context assembled

    6 sources observed · npm test → 2 failures

  3. 23:12:47

    Redaction applied

    2 items · API keys · tokens

  4. 23:13:15

    Review completed

    17 items confirmed · 0 unapproved

  5. 23:14:08

    Context package frozen

    17 items · 4,810 tokens · 7e3b0f…a91c

  6. 23:14:21

    Provider request approved

    4,810 tokens → Anthropic · Claude

  7. 23:14:39

    Plan received

    3 typed actions

  8. 23:15:04

    File write approved

    src/auth/session.ts · +14 −7

  9. 23:15:16

    Verification complete

    PASS · npm test → 0 failures

Browser context, only when you say so.

Browser context is captured explicitly - you pick the tab and the text. It is scoped to the project and appears in the Context Preview like any other source. There is no silent browser monitoring.

BROWSER CONTEXT · EXPLICIT CAPTURE

MANUAL

Selected tab

OAuth callback - auth flow debug

dev.local:3000/oauth/callback · title + selected text only

No silent browser monitoring. No cookies, storage, screenshots, or mouse input. Captured content is scoped to the current project and appears in the Context Preview like any other source.

Evolution Lab

EXPERIMENTAL

Bounded, deterministic graph modules evaluated locally inside a sandboxed interpreter. Candidates, scores, and a selected module - no filesystem, no network, no credentials, no arbitrary processes. The best module is folded into a Guide; nothing executes automatically.

EVOLUTION LAB · EVAL RUN 0x2F

EXPERIMENTALbounded interpreter

Flow

  1. Dataset
  2. Graph candidates
  3. Evaluation
  4. Selection
  5. Best module

Evaluation readout

local · bounded · deterministic

epoch 0 → 24score converging · best 0.94

generation

24

candidates

128

best fitness

0.94

evaluations

4,096

selected module: session-guard-v9 · fitness 0.94

sandbox:No filesystemNo networkNo credentialsNo process executionDeterministic evaluation

See the full context pipeline for yourself.

Request AccessExplore Security