Arafadh

Arafadh coding-agent extension. Extension ini memakai Cline SDK secara lokal untuk tool workspace dan gateway produksi Arafadh untuk autentikasi, model routing, usage, serta kredit. Provider API key tidak pernah dibundel ke extension.

Multi-turn conversations in 0.2.0

Arafadh 0.2.0 adds local, persistent multi-turn conversation support to the VS Code sidebar. Conversation history is used to seed follow-up prompts in the same chat while keeping approval and cancellation behavior intact.

Riwayat chat tetap tersimpan lokal per profil VS Code. Login, katalog model, saldo kredit, dan request coding agent memakai akun Arafadh yang sama melalui endpoint /api/v1/extension/*.

Conversation storage

Conversation records are stored under VS Code extension global storage using ExtensionContext.globalStorageUri, in a conversations subdirectory. History is not written to the user's workspace, .vscode folder, or project repository.

The storage layer validates data when loading it. Missing or empty storage starts from a clean state. Corrupted JSON is quarantined on a best-effort basis and the extension falls back to an empty conversation state so activation can continue.

Persisted conversation data survives extension reloads and VS Code restarts on the same machine/profile.

Conversation lifecycle

The implemented lifecycle is:

New Chat
→ active conversation
→ user prompt persisted
→ runtime session
→ streaming
→ assistant final message persisted
→ next prompt uses same conversation context

Before the first prompt, a chat is titled New Chat. After the first prompt, the title is derived deterministically from the beginning of that prompt without calling a model.

Context strategy

Follow-up turns use a deterministic context builder. The current user prompt is always preserved and sent as the runtime prompt. Prior user, assistant, and safe tool summaries from the active conversation can be sent as SDK initialMessages.

The default context budget is:

• maximum seeded history messages: 40
• maximum seeded history characters: 24,000
• maximum characters per seeded message: 4,000

When history exceeds the budget, older messages are removed deterministically and an explicit truncation marker is inserted. V1 does not call an extra model for summarization and does not provide semantic long-term memory.

Workspace isolation

Conversations are isolated by canonical workspace key. A conversation created in workspace A is not automatically included as context in workspace B. No-workspace chats are also kept separate from workspace-backed chats.

Tool history

Tool activity is persisted as safe summaries instead of raw sensitive payloads. Tool statuses may be:

requested
approved
rejected
completed
failed
cancelled

Rejected or failed tools are not represented as successful completions in future context.

Security notes

Conversation persistence redacts common secret-shaped values before storing or seeding history, including bearer tokens, authorization headers, provider API key patterns, access tokens, secret keys, passwords, and similar assignments.

The development access token remains in VS Code SecretStorage under arafadh.stable.accessToken; it is not stored in conversation history. Provider API keys are not embedded in the extension package.

The sidebar renders conversation titles and message content with DOM text APIs rather than unsanitized innerHTML. Tool approval policy remains active for mutation and command tools.

Known limitations

• Conversation history is local-only.
• There is no backend sync or multi-device history.
• There is no semantic memory or model-generated summarization.
• Long history is reduced by deterministic truncation.
• Model tool selection remains nondeterministic.
• Concurrency is intentionally limited to one active running session.
• Riwayat percakapan belum disinkronkan lintas perangkat.
• Image/file generation dan beberapa kontrol lanjutan tetap tersedia melalui Web Arafadh.
• Manual real-model smoke testing is still required before wider use.