Pulse.ai
Pulse.ai
A Digitide Product
Loading…
Sign in
Welcome to Pulse.ai

1 of 5
1 / 6
Welcome to Pulse.ai

Build Chat
$0.00
0
No chat selected
no documents indexed yet
loading agents…
Workspace

Agents

Define personas and which MCP tools each can use.
Name Kind Description Capability Actions
Workspace

Tools

Build, edit, and review tools the agents can call.

Authorized tools

Name Source Description Parameters Actions
New tool
focused mode
Knowledge

Knowledge graph

Entities + relations extracted from your documents and stored in Neo4j. Click any node or edge to inspect properties and provenance.

From Relation To Confidence Source document
Knowledge

Knowledge base

Upload documents and review which storage backend each one lives in.
Upload documents

Supported: .pdf (text + tables + images), .txt, .md, .csv, .json, and other text-like formats. Max 10MB per file. Pick one or many; each file is indexed twice: legacy TF-IDF (keyword) and the agentic vector store (semantic chunking + multi-modal + Chroma embeddings).

Agentic RAG (vector store) 0 chunks

ChromaDB + ONNX MiniLM-L6-v2 embeddings. Multi-modal ingestion via PyMuPDF extracts text, tables, and images (with caption-text proximity). The Knowledge Researcher agent uses agentic_rag_search for hybrid retrieval.

Quick query test
Knowledge graph (Neo4j) 0 entities · 0 relations

Every uploaded document is automatically mined for entities (companies, people, places, treaties, policies…) and relations (PARTY_TO, OWNS, CEDES_TO, REGULATED_BY…) which are persisted into the Neo4j graph at bolt://localhost:7687. Agents enrich agentic_rag_search results with a 1-hop graph context when a query matches known entities.

Per-document breakdown
Document Entities Relations Top kinds
no extractions yet

Indexed documents

Name Type / Size Stored in Status Actions

Long-term memory

Durable cross-conversation facts, preferences, and notes. Agents recall_memory at turn start and remember_fact when the user fixes a decision.
0 items
Add memory manually
Recall test
All memory

Costs

Per-thread spend, ingestion, and per-user attribution.
DocumentUploadedSizeChunksGraphContextCost
UserThreadsTurnsCostLast activity
Call trace ·

Workflow Builder

Compose multi-agent use-cases: chain agents with explicit inputs, output schemas, verifiers, and branching. Test and govern each one.
Drag-and-drop designer

Compose agents, verifiers, branches and tools on a horizontal canvas — like Langflow / Agent Builder.

Live trace + replay

Every run streams reasoning, tool calls and tool results in real time. Step through old runs node-by-node.

Verifiers + governance

Add yes/no gates, JSON-schema validation, and "no-data" routing so chains don't blindly continue.

Per-step cost + tests

Track wall time and cost per node. Save assertions; run regression tests across all of your workflows.

Name Nodes Last run Last cost Runs Actions
No workflow selected

Pick one from the switcher or create a new workflow.

Traces · (pick a workflow)
Each trigger run is recorded as a trace — every step's input/output, cost, and timing is replayable.
Trace history
Select a trace on the left to see step-by-step execution and play it back.
New test case
Test cases
Node reference
  • trigger — auto-created entry point. Receives the run-time input.
  • agent — invokes one of your registered agents. Set instructions, tool subset, and output schema. Output is parsed against the schema before being passed downstream.
  • tool — direct MCP tool call (no model in the loop). Use for deterministic data fetches.
  • verifier — agent node specialised for output validation; given the upstream output, returns {ok, reasons}. If ok=false, the run halts and the failure is recorded.
  • branch — if/else gate based on a JSON-path or substring match against the upstream output.
  • end — terminal node. Captures the final output for the run record.
Output schemas
  • text — free text (default).
  • yes_no — must contain yes or no.
  • enum: a,b,c — must be one of the listed values.
  • json — must parse as JSON.
  • json_schema: {...} — must match the given JSON schema.
Drag-and-drop canvas

Currently the builder is a structured list editor (every node has a numbered position; connections reference other node IDs). A visual canvas with drag-and-drop is on the v2.x roadmap and will read/write the same JSON.

Workflow Wizard getting started
The proposed workflow will appear here once I have enough to draft.
Understanding your requirement…
Step 1 of 7.
Walkthrough
    Test workflow
    1 Sample input
    2 Execution trace
    3 Verdict & notes
    Sample input
    The AI drafts a realistic input for this workflow. Edit it if you want, then click Run test.
    Execution trace
    What each node did, in order.
    Did it meet expectations?
    Your feedback is saved with this workflow so future tests can compare.
    Saved.
    Workflow paused · your input needed

    Loading…

    Loading workflow context…
    What we need from you
    What's been done so far · what happens next
    Completed
      Next, once you decide
        Your decision
        Click one of the buttons above to make your choice, then press Submit.
        Click one of the buttons above to make your choice, then press Submit.
        Submitted. The workflow has resumed — you can close this tab.

        AI Call Center

        Design voice agents that callers can talk to in the Call Center Portal. Each agent has a goal, a slice of your knowledge base, and tools it can call (e.g. ticketing).
        Open portal
        Agents published here appear on the Call Center Portal. To let a caller join, click Generate OTP on the agent and share the access code (single-use, 15-minute TTL). To add the included ticketing tool, set its MCP URL to http://localhost:8200/mcp.

        New voice agent

        Knowledge base (agent-private)
        Docs uploaded here are scoped to this agent only. Click Upload on a new agent and the agent is saved automatically first.
        No private docs yet for this agent.
        Tools
        Pick the tools this agent is allowed to call. The catalog comes from the central tools registry (admin-managed). Leave everything checked for "no restriction".
        Loading catalog…

        Governance

        End-to-end audit trail: prompt-injection scans, budget breaches, canary checks, tool authorisations, and per-thread traceability.
        Security events

        Dashboard

        Pulse.ai at a glance — what admin should know right now.
        Loading dashboard…
        Recent activity (last 24h)
          Top agents (turns)
            Spend (last 7 days)

              Admin

              User management, departments, role groups, agent access control, and feedback review.
              All users
              EmailDisplay nameRoleDepartmentDept adminLast login
              New department
              All departments
              Grant access
              Rule of thumb: an agent with no rules is visible to everyone. Add a rule to restrict it.
              Active rules
              New role group
              All groups
              Select a role group on the left to drill in and edit its permissions.
              LLM backend

              Saved profiles let you flip between providers (Claude / gpt-4o / gpt-5.x …) with one click. Pick a profile in the list, click Set active, then restart pulse-web — the dispatcher picks up the active profile at boot. Empty key fields preserve the previously-saved secret.

              Profiles
              Label Provider Deployment / endpoint Keys Actions
              loading…
              Edit profile
              Azure OpenAI
              Anthropic
              Optional locally if the local claude CLI is already logged in; required on cloud / headless.
              System configuration

              Live runtime status of the database and Neo4j connections. Edits are persisted to web/data/.env.local; real environment variables set in the launching shell always win. A restart is required for changes to take effect.

              Saved. Restart the server (python3 web/app.py) so the new values are loaded.
              Database
              Active URL
              Source
              Local-dev default
              Leave blank to use the local-dev default above (when reachable) or fall back to SQLite.
              Neo4j knowledge graph
              Connectivity
              User feedback queue

              My preferences

              Personal style/format preferences agents will honour in your conversations.
              Add preference
              Your saved preferences
              Department mandates
              (loading…)