4 findingsStatic scanned
Puts Claude in your terminal to understand your codebase, edit files and handle git workflows.
80.2M installs/moSEE LICENSE IN README.md
T2tx Iris
t2tx · App
Iris connects a Slack workspace to a local agent command line, Claude Code by default. Each Slack thread or direct message maps to one agent session that keeps running, streams its output back and is resumed by the next message if its process has ended. The agent's tool permission requests appear as Allow and Deny buttons in Slack. You host it yourself with your own Slack bot and app tokens, it ignores channels and users you have not listed, and the agent command line must already be signed in because Iris does not handle API keys.
Written by ooruby from the README of @t2tx/iris 0.4.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You can steer a coding agent running on your own machine from Slack, including approving its tool requests.
What you could do with it
- Mention it in a Slack channel to start a Claude Code session and follow its progress in the thread.
- Approve or deny a tool request from your agent by clicking a button in Slack.
- Send different Slack channels to different project folders, each with its own permission mode.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Slack ⇄ Claude Code bridge (minimal, self-hosted). Socket Mode + Bolt.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.4.2, the file with digest sha512-tSdYG32NuhhJ1lq4aSlOPEbpo9gBKv+Le0zkHXursyBsEQhiu7H5J30UNndAn2/yR54lkY/SnXHv7S58bXH/eg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @t2tx/iris@0.4.2Pinned to 0.4.2, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @t2tx/iris
- Version read
- 0.4.2
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/t2tx/iris
- Commit
- ca1b39661846
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/t2tx-iris)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
Similar apps
All appsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.