Namera

Namera is a programmable session key layer for smart wallets. It enables wallets to delegate scoped permissions through session keys with programmable policies, designed for agents, automation, and multi-chain execution.

Contents

• Namera
  • Contents
  • Monorepo Structure
    • Apps
    • Packages
  • Documentation
  • Quick Start
    • Prerequisites
    • Installation
    • Development
  • Contributing
    • Development Workflow
    • Commit Convention
    • Versioning and Releases
  • Security
  • License

Monorepo Structure

Namera is organized as a Turborepo monorepo using Bun as the package manager.

Apps

Package	Description
apps/cli	CLI for managing accounts, sessions, wallets and running local MCP server
apps/docs	Developer documentation built with Fumadocs + Tanstack Start

Packages

Package	Description
packages/sdk	Core TypeScript SDK for smart accounts, session keys, policies, and transaction execution
packages/config	Centralized configurations (tsconfig, Biome, Vitest, tsdown)
packages/ui	Shared UI components

Documentation

Full documentation is available at namera.ai/docs.

• SDK Docs — smart accounts, session keys, policies, transactions, signing
• CLI Docs — keystore, smart account, session key commands, MCP server
• Getting Started — end-to-end guide from installation to first transaction

Quick Start

Prerequisites

• Node.js 18+
• pnpm: npm install -g pnpm

Installation

Clone the repository and install dependencies:

gh repo clone thenamespace/namera
cd namera
pnpm install

Development

Start all apps in development mode:

pnpm run dev

Build all packages and apps:

pnpm run build

To build a specific package or app:

pnpm run build --filter=@namera-ai/sdk
# or
pnpm run build --filter=@namera-ai/cli

Lint and format:

pnpm run lint
pnpm run lint:check

Contributing

Contributions are welcome. Please read the guidelines below before submitting a PR.

Development Workflow

1. Fork the repository and create a branch for your changes
2. Install dependencies with pnpm install
3. Make your changes and ensure tests pass
4. Run linting with pnpm run lint
5. Open a pull request against main

All PRs should:

• Follow the existing code style (Biome enforces this)
• Use Effect patterns (Effect.gen, @effect/schema for validation, tagged error classes)
• Include tests where applicable
• Pass CI checks

Commit Convention

This repo uses Conventional Commits. Commit messages should follow this format:

<type>(<scope>): <description>

Common types:

• feat: new feature
• fix: bug fix
• docs: documentation changes
• chore: tooling, config, or maintenance
• refactor: code changes that do not fix bugs or add features
• test: adding or updating tests

Example:

feat(sdk): add passkey session key support
fix(cli): resolve keystore decryption edge case
docs: update session key policy examples

Commitlint is configured via lefthook and will validate commits automatically.

Versioning and Releases

This repo uses Changesets for versioning and publishing.

To version packages:

pnpm run changeset

Changesets will guide you through selecting the version bump (major, minor, patch) for each package. The CI pipeline handles publishing when a release PR is merged, and approved by a maintainer.

Security

Please report security issues via GitHub Security Advisories: https://github.com/thenamespace/namera/security

Do not open a public issue for security vulnerabilities.

License

Apache 2.0. See LICENSE.