Sign in
Local development mode. This is a fake login, not a real identity provider. Enter any organization and user id.
This becomes your tenant.
Enter your email, then choose how to sign in.
Signing in as
Your organization uses single sign-on.
Signing in as
At a glance
Documents indexed
Workspaces
separate spaces for your context
Context served
Changes written
notes, proposals, and commits
On disk
Last activity
Counts come from this organization's index and audit log. Nothing here reads your documents.
Connect your agent
Point your coding agent at this address. Connect with a token from the Integrations tab, or with browser sign-in where available.
Your agent signs in with your browser (no token to paste) to read and propose across your whole organization, with workspaces you add later included automatically. To let it commit changes, or to set what it can do in a specific workspace, use the Workspaces tab. Commit access works the same for a browser sign-in or a token.
- Agent sign-in is on by default for organization owners.
- Open Settings, then Connectors in claude.ai or Claude Desktop and choose Add custom connector.
- Paste your organization address (the MCP URL above) and save.
- Connect and sign in with your browser; no token to paste.
Step 2: make your agent prefer Contexel
Prefer to let your agent do it? Paste this prompt and it will write the rules file itself (it calls the Contexel setup tool).
Agents follow project rules more reliably than server hints, so this is the surest way to make yours use Contexel.
Step 3: the Contexel plugin (optional, strongest for Claude Code)
A Claude Code plugin bundles the Contexel MCP connection (Step 1) plus a skill and a light session-start reminder, so your agent connects, checks Contexel first, and saves durable notes here instead of its own local memory.
Install it in one step. In Claude Code, run:
/plugin marketplace add contexel/contexel-plugin /plugin install contexel@contexel-plugin /reload-plugins
Source: github.com/contexel/contexel-plugin. It is generic, so your workspace list still comes from the Step 2 rules file.
Ask your organization
See the exact context an agent would get for a question, each piece with its source. A read-only preview of your saved context, not a chatbot; nothing is changed.
Knowledge health
A read-only scan for knowledge that can mislead your agents, and for knowledge that never arrived: notes that were saved but never captured, conflicting standards, replaced documents still kept, documents nothing can retrieve, documents that point at a subject which isn't here, thin names that searches miss, and searches that found nothing. A fix is queued for review, or applied directly if you have commit access to the workspace.
Workspaces
A workspace is a separate space for a project, client, or team. Your agent sees only the workspaces its token or sign-in allows, and context never crosses between them. Give each a type and short description so it knows what belongs where.
Approve or reject what your agents proposed, and see what recently changed, for the workspaces you own.
Review queue
Proposals from your agents, each with the exact diff. Accept commits the change to its workspace; Reject sets it aside with no change.
Recent changes
Recently added, updated, or retired knowledge, from your team's edits and your agents' approved changes.
GitHub repositories Coming soon
Connect a repository and Contexel will mirror it read-only, index its markdown, and serve it to your agent as context. Not available yet; nothing is connected or indexed today.
- Install the Contexel GitHub App and pick repositories.
- Connect each repository to a workspace from the Workspaces tab; context never crosses workspaces.
- Contexel mirrors the markdown read-only and keeps it in sync.
Agent tokens
A token is how your agent connects. Give it a name, create it, then grant it access to specific workspaces from the Workspaces tab, the same place you give people access. You see the tokens you created; an organization admin sees everyone's.
A label so you can tell your tokens apart. It grants no access on its own.
The setup commands on the Overview tab now include this token. Give it access to a workspace from the Workspaces tab.
| Name | Owner | Token id | Access | Status |
|---|
Import what your team already wrote down
Paste a CLAUDE.md, AGENTS.md, or any notes file. Contexel splits it into separate memories, one per section, so your agent gets just the relevant parts on demand.
Now try asking your agent (or the get_context tool) something like:
Import a transcript
Paste a meeting transcript. Contexel extracts the commitments, decisions, and lessons; secrets are stripped first. With commit access to the workspace they're added directly; otherwise each is queued as a proposal for your review.
Organization members
People who belong to this organization. Invite a teammate by email, change their role, or remove them. Members share this organization; admins can also manage members and settings.
| Member | Role | Status | Actions |
|---|
Encryption
Your documents and search index are encrypted at rest with a key dedicated to your organization. It is never shared with other customers.
Your search index is encrypted at rest with a key dedicated to your organization. Your documents are not yet encrypted with this key.
Contexel keeps a copy of your key to run indexing and search, which means we can technically access your data. To hold the key yourself, switch below.
Currently protected by platform storage encryption and access controls. Turn encryption on to encrypt your documents and search index with a key dedicated to your organization.
After you switch, Contexel has no way to decrypt your documents or your search index. You enter your key each session. If you lose the key, your data cannot be recovered.
Contexel has no way to decrypt your documents or your search index. You hold the key. It stays in this organization's memory only while unlocked and is never written to disk.
Backups taken before you switched may retain a copy until they expire.
This organization is locked. Contexel has no way to decrypt your documents or your search index. Reads and writes are refused until you unlock it with your key.
Platform admin
Every tenant on this deployment: account details, storage used, encryption status, and activity from the audit log. Never the tenant's content itself.
| Tenant | Org | Name | Created | Status | Last login | Users | Content | Index | Total | Encryption | Reads / Writes / Denials | Last activity | Actions |
|---|