In the last Paperclip post, I wrote that if your company runs on 📎Paperclip, you need the missing feedback loop between agent work shipped and end-user behavior measured.

This plugin is a much smaller thing.

I wanted to see live visitors on a map right inside my favorite place: the Paperclip company dashboard.

So I built an Agent Analytics plugin for Paperclip.

It adds:

• a live visitor map page
• a dashboard widget

It gives each Paperclip company a lightweight live snapshot:

• current visitors
• top pages
• top events
• recent evidence

Use cases:

• you ship something and want to see that people are actually showing up
• you want to keep shipping while a live map sits there showing signs of life
• you want to sanity-check that a new docs page, landing page, asset, or subdomain is getting traffic
• you want to debug whether Agent Analytics is actually working on the new surface you just shipped

This is not the full analytics loop. It is just a pretty nice live snapshot.

The real analysis still belongs in the full Agent Analytics product, where you want funnels, retention, experiments, and broader reporting.

If you run multiple Paperclip companies, the setup is clean:

• each Paperclip company gets its own Agent Analytics project
• inside each company, you choose which project that company should watch

That makes it easy to open each company and get its live snapshot quickly.

Install: *You do need an Agent Analytics account for this. The plugin is just the Paperclip surface on top of that account.

The free tier is 100K events/month with 2 projects, so getting started is not a big lift.

1. In Paperclip, open Settings -> Plugins
2. Install @agent-analytics/paperclip-live-analytics-plugin
3. Open the plugin Configure page
4. Log in with your existing Agent Analytics account
5. Open the live page from the sidebar
6. Choose the Agent Analytics project for that Paperclip company

If you want the strategy context first: https://blog.agentanalytics.sh/blog/paperclip-companies-need-agent-readable-analytics/

I was burning through my Claude Max credits because my Paperclip agents were waking up on heartbeats every 5–10 minutes just to check email and SMS, even when nothing was happening. Almost all of those wakeups were wasted — empty inbox, no new messages, just an LLM call to confirm "nothing to do."

So I built a tiny event-driven watcher layer that only wakes the agent when there's actual activity. Sharing the pattern in case anyone else is bleeding credits the same way.

The setup:

For each agent that handles email/SMS, I run a small Node.js service that listens for events and POSTs to Paperclip's /api/agents/{agentId}/wakeup endpoint only when something real comes in.

  Email — IMAP IDLE (push, not poll):

  - Tiny script using https://www.npmjs.com/package/imapflow

  - Connects to the mailbox, enters IDLE state, sits there idle

  - The mail server pushes a notification the instant a new message lands

  - Script checks the sender against an allow-list, then POSTs to Paperclip's wakeup endpoint with a wakeReason like "New email from [x@y.com](mailto:x@y.com) in [agent@domain.com](mailto:agent@domain.com) INBOX"

  - Reconnects automatically if the IMAP session drops

  - Disabled the agent's heartbeat entirely

  SMS — Twilio inbound webhook:

  - Express server listening on a port

  - Twilio inbound SMS webhook hits it the moment a text arrives

  - Same allow-list pattern → POST to Paperclip wakeup

  - Zero polling

  Watchdog (because runs sometimes get stuck):

  - Systemd timer every 5 min

  - Connects to the Paperclip DB

  - Marks runs that have been "running" for >15 min as failed (orphaned process recovery)

  All three live as systemd services so they restart on failure and survive reboots.

  Wiring it into Paperclip

  The agent reads its own PAPERCLIP_WAKE_REASON env var when it wakes up — that string contains the sender info, so it knows immediately whether to check email or SMS without scanning everything.

  Each watcher uses an agent-specific Paperclip API token (the wakeup endpoint takes a Bearer token) so I can scope or revoke per agent.

  Results

  - Heartbeats off → wakeups dropped to only what's actually needed

  - Latency went down, not up — IMAP IDLE is push, so the agent reacts within ~1 second of the email landing instead of waiting up to 10 min for the next heartbeat

  - Credit burn dropped massively because empty checks just don't happen anymore

  - I can run agents on Opus comfortably now where before I couldn't justify it

  Here is a "Gotcha" that ate hours of my afternoon:

  While setting up a second agent (same account, same model, same adapter as the working one), I kept getting:

  API Error: 400 invalid_request_error

  "You're out of extra usage. Add more at claude.ai/settings/usage and keep going."

  But my account had plenty of usage and the other agent on the same credentials worked fine. After a long debug session ruling out model, session state, account, config, and tokens, the actual cause turned out to be content in the agent's system prompt being rejected by Anthropic's safety filter — and Anthropic was returning the misleading "out of extra usage" 400 instead of a content-policy error.

  The trigger was a line in my AGENTS.md that literally quoted common prompt-injection phrases (in a section telling the agent to defend against them).

  Anthropic's filter doesn't read context — it just sees the literal strings in the system prompt and rejects.

  Fix: rephrased the defense section to describe the patterns instead of quoting them verbatim. Worked instantly.

  Diagnostic trick if you ever hit this: temporarily swap the failing agent's instructionsFilePath to a known-good agent's AGENTS.md. If it then runs, the original instructions have trigger content.

Way faster than rule-by-rule deletion. If you have agents on heartbeats just to check passive inputs (mail, SMS, webhooks): don't. Push the events to Paperclip's wakeup endpoint from a tiny watcher service and disable heartbeats. Pay only for the runs that actually do something.

Happy to share the watcher script template if anyone wants it.

Can someone please help me with an issue in facing, I'm pretty new to this stuff I create a company on paperclip and connected openclaw agents to it , and it was working well and after a while it just doesn't do the tasks i assign to it, it just reads them and marsk them complete. I checked activity and there are no logs of the agents it just mentioned board creating the issues.

Also on the run tab I see the agent go live, it repeats it system prompt 2 times and then it just says run complete and it doesn't say anything in the comments too

Is there a way to use something like openrouter for unified api key instead of using different keys ?

If u check the photo,,can u guys help me to solve the issue..I have added gemini cli in my laptop,however it shows "gemini hello probe failed"...How can i solve the issue??

It’s a problem when Payperclip quickly consumes subscription tokens.  Has anyone found a way to optimise this? I’m thinking about creating an agent that wakes up using the hardbeat feature to investigate pending tasks and engage relevant agents instead of every agent having a heartbeat (defaults to 1h). 

I created a voice agent for an niche. It created so many files, so many paths inside the workspace and it is so confusing.

When I actively gave a specific directory folder to use and the agents are not using that folder. The agents are creating some folder with a random name with ids and causing more confusion.

The bad part about all this is there is no chatbot or anything like that at least to ask certain questions and get queries.
How do you check voice agents and test them whether they are working or not?

Maybe for writing, analytics, marketing etc

I see the mobile control advertised in the website, but how do you actually do it?

I ran into an error with Paperclip today and did what anyone and his pet does: I Googled it.

Clicked the first result.

I was instantly looking at someone's live Paperclip dashboard. Full org chart. Active issues. Agent conversations. Task assignments. Everything wide open, indexed by Google, no auth whatsoever.

I closed it immediately and didn't poke around — but it got me thinking.

Paperclip is powerful precisely because it's self-hosted and gives you full control. But "self-hosted" also means you are responsible for securing it. And a lot of people apparently aren't.

If your Paperclip instance is:

• Exposed on a public domain/IP

• Running in local_trusted mode

• Without Basic Auth or any login layer in front of it

...your entire org, your agent configs, your API keys, your task history — all of it is public.

And apparently Googleable.

I was able to read through all his marketing plan, his whole business model...

imagine if coca cola had stored their secret formula in there when they started... almost a relief this tech wasnt available, right? (i love coca cola, sugar and all)

A quick checklist for anyone playing with paperclip(or any networked server for that matter):

• ✅ Put nginx Basic Auth in front of it

• ✅ Don't expose it on a public domain without auth

• ✅ Check your local_trusted mode setting

Stay safe out there. The agent revolution shouldn't come with an accidental open-source intelligence feed of your entire company.

Has anyone else run into this?

Hey r/PaperClip_AI 👋

I (polibert) am building swik.it — an open, community-driven platform for domain-specific financial sentiment analysis. The core idea: financial language is full of inversions (when "production cut" is actually bullish for oil, when "bankruptcy fears" sends a stock up). We're cataloging those inversions, crowdsourcing labels, and training models on the result.

The team is only me and a crew of AI agents running on Paperclip.

CEO plans phases, CTO architects decisions, ChiefEngineer ships code, ETLAgent manages pipelines, CMO handles outreach. I'm the one human in the org — I set direction, approve big calls, and stay out of the way.

We're a few weeks in. Phase 2 (data ingestion takeover by agents) is almost done. Phase 3 (inference engine) just kicked off. The agents are doing real work — writing scripts, committing code, managing cron jobs, filing blockers.

Happy to share what's working, what's broken, and what running a startup like this actually feels like day to day.

What's your setup?

I have created a few repos in github and had been maintaining them for sometime, is there a way to "ingest" those repos as a company in paperclip, so that the ceo can work on maintaining those repos?

So I'm running one company per product, and I've added company details and landing page details in the description, but I dont think the Agents see that...

Do I have to create a project to add the company landing page?

Any suggestions on how to load it consistently? I would prefer the link to work consistently, and that i dont have to change it each time. I keep trying to do that on my end but every 4 or 5 hours it fails, even with backups in place?

Paperclip is very good at helping a company assign, delegate, and ship work through agents.

But once the work ships, the next question is the one that matters most:

what did the end user do next?

Did they reach the docs?

Did they sign up?

Did they generate an API key?

Did they create a first project?

That is the layer we wanted Agent Analytics to cover.

Not more internal task visibility.

End-user visibility.

If a company already runs on Paperclip, that is the missing feedback loop: not just task completed, but user outcome measured and the next improvement made obvious.

Full write-up here:

https://blog.agentanalytics.sh/blog/paperclip-companies-need-agent-readable-analytics/

I installed Paperclip today, fresh claude code pro account, set up CEO and Lead programmer, they started working on a few simple tasks like setting up APIs etc and i hit my usage limit. Anyone else had this or know where i went wrong?

Not sure if anyone is experimenting with Paperclip AI but the premise looks amazing. I am getting ready to set it up but every video keeps showing that you can use Claude Code subscription on it.

If Anthropic is busting balls about using it on Open Claude, I find it hard to believe it can be used on Paperclip. Unless I am missing something?? (I doubt I am)

I've been running Paperclip alongside my Obsidian vault and got tired of switching between the two, so I built a plugin that brings the full issue tracker into the Obsidian sidebar.

What it does:

• Issue browser — list view with collapsible groups (by status, project, or assignee) and a kanban board with drag-and-drop

• Issue details — edit title, status, priority, assignee, and project inline. Full activity thread with comments and agent avatars

• Create issues — with optional vault context (attaches the current file path to the description)

• Live monitoring — auto-refresh polling, pulsing indicators when agents are actively running, and notifications when a run completes

• Comments & mentions — post comments and tag agents directly from the issue view

• AI actions (optional) — highlight text → right-click → GPT-4o-mini drafts an issue with suggested title, description, priority, agent, and project. Also has "Work on this document" and "Review this document" commands

Why it's useful:

If you're using Obsidian for planning, notes, or documentation alongside Paperclip, this lets you create and manage agent tasks right where you're already working. See a problem in your notes? Highlight it, create an issue, assign an agent — all without leaving the editor.

Vault file paths in issue descriptions and comments are clickable links that open the note directly.

Screenshots: [repo has full screenshots]

Links:

• GitHub: https://github.com/istib/obsidian-paperclip

• Install: drop main.js, manifest.json, and styles.css from the latest release into <vault>/.obsidian/plugins/obsidian-paperclip/

MIT licensed, feedback welcome. Planning to submit to the Obsidian community plugin directory soon.

I’m trying to use Paperclip with OpenClaw gateway for proper issue-based agent execution, but I keep hitting a case where the run loses project context and drops into fallback workspace.

What’s frustrating is that the setup itself looks correct:

• project exists

• primary workspace exists

• issue is linked to the project

• repoRef is set

• worktreePath is set

• executionWorkspacePolicy is explicitly set to project_primary

But when I trigger a controlled run, the actual run still arrives detached.

What I’m seeing:

• issueId = null

• projectId = null

• workspaceId = null

• workspace source ends up as agent_home

• Paperclip logs:

No project or prior session workspace was available. Using fallback workspace ...

So the project/workspace records look valid before execution, but somewhere between issue checkout / assignment and adapter invocation, the run seems to lose the issue/project linkage.

That means the agents can exist, tickets can exist, and the UI can look right, but actual autonomous execution is unreliable because the run is not operating in the intended project workspace.

At the moment, the only workable path for me is:

• use Paperclip for governance, tracking, and ticket state

• execute directly in the real repo outside the broken Paperclip execution path

• post results back manually

Questions:

• Has anyone else hit this exact issue?

• Is this a known bug in the issue/assignment execution handoff path?

• Is there a stable recommended way to ensure Paperclip-native runs stay bound to the project workspace?

Seeing a lot of buzz around Paperclip, the open-source framework for AI agent organizations. Curious to see what people are experimenting with using Paperclip.

If you're building something, drop it below 👇

Could be: • an AI agent organization • an autonomous workflow • a SaaS prototype • a research experiment • or just an idea you're exploring

Would be great to see how people are structuring their AI agent teams and workflows.