Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Sichere ProgrammierungWhat is Programming And How i can Enjoy it?(24.09.2026 um 11:54 Uhr)
Sichere ProgrammierungYou Don't Need Adobe Commerce Cloud to Survive Black Friday(24.09.2026 um 11:55 Uhr)
Malware / Trojaner / VirenBeyond Lazarus: Organization of DPRK cyber capabilities(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenBeyond Lazarus: Organization of DPRK Cyber Capabilities(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenThe fake worker threat and the rise of human infiltration(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenPolinRider Spreads Through Compromised GitHub Accounts and Packagist(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenWeaselBiscuit Strips BeaverTail and OtterCookie Down to Essentials(24.09.2026 um 11:59 Uhr)
Sichere ProgrammierungWhat is Programming And How i can Enjoy it?(24.09.2026 um 11:54 Uhr)
Sichere ProgrammierungYou Don't Need Adobe Commerce Cloud to Survive Black Friday(24.09.2026 um 11:55 Uhr)
Malware / Trojaner / VirenBeyond Lazarus: Organization of DPRK cyber capabilities(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenBeyond Lazarus: Organization of DPRK Cyber Capabilities(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenThe fake worker threat and the rise of human infiltration(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenPolinRider Spreads Through Compromised GitHub Accounts and Packagist(24.09.2026 um 11:59 Uhr)
Malware / Trojaner / VirenWeaselBiscuit Strips BeaverTail and OtterCookie Down to Essentials(24.09.2026 um 11:59 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

How to use Llama3.2 to write daily logs in Notion based on your screen

Ever wished you had a personal AI assistant that could keep track of your daily work? With screenpipe & llama3.2, you can now automate the process of writing detailed logs based on your screen activity. Let's dive into how you can set…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!





Ever wished you had a personal AI assistant that could keep track of your daily work? With screenpipe & llama3.2, you can now automate the process of writing detailed logs based on your screen activity. Let's dive into how you can set this up using screenpipe's plugin system.






What is screenpipe?



screenpipe is an open-source tool that captures your screen and audio 24/7, extracts text using ocr, and allows you to build personalized ai-powered workflows. It's designed to be secure, with your data staying on your machine.






Installing screenpipe



(If you're not on macOS check these instructions)



To build the screenpipe app from source on macOS, follow these steps:




  1. Install Rust and necessary dependencies:




curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
brew install pkg-config ffmpeg jq tesseract cmake wget







  1. Install Deno CLI:




curl -fsSL https://deno.land/install.sh | sh







  1. Clone the screenpipe repository:




git clone https://github.com/mediar-ai/screenpipe
cd screenpipe







  1. Build the project:




cargo build --release --features metal







  1. To build the desktop app, first add this to your VSCode settings in .vscode/settings.json:




{
"rust-analyzer.cargo.features": [
"metal",
"pipes"
],
"rust-analyzer.server.extraEnv": {
"DYLD_LIBRARY_PATH": "${workspaceFolder}/screenpipe-vision/lib:${env:DYLD_LIBRARY_PATH}",
"SCREENPIPE_APP_DEV": "true"
},
"rust-analyzer.cargo.extraEnv": {
"DYLD_LIBRARY_PATH": "${workspaceFolder}/screenpipe-vision/lib:${env:DYLD_LIBRARY_PATH}",
"SCREENPIPE_APP_DEV": "true"
},
"terminal.integrated.env.osx": {
"DYLD_LIBRARY_PATH": "${workspaceFolder}/screenpipe-vision/lib:${env:DYLD_LIBRARY_PATH}",
"SCREENPIPE_APP_DEV": "true"
}
}







  1. Then, build the desktop app:




cd screenpipe-app-tauri
bun install
bun scripts/pre_build.js
bun tauri build






This process will build the screenpipe app from source on your macOS system. If you encounter any issues, you can open an issue on the GitHub repository for assistance.



Start screenpipe by clicking start or through CLI in dev mode:



Image description



Once you installed screenpipe, add this plugin by dropping this URL in the "add your own pipe" bar:



https://github.com/mediar-ai/screenpipe/tree/main/examples/typescript/pipe-phi3.5-engineering-team-logs



Use llama3.2:3b-instruct-q4_K_M as model.



You should also create and configure your Notion integration (instructions on the plugin page in screenpipe app).



Start the LLM in the settings (or manually through Ollama):



Image description



If you are on Windows or Linux you need to run Ollama yourself.



Restart screenpipe by clicking stop and start or through CLI in dev mode:



Image description



You should start getting notifications in screenpipe AI inbox:



Image description



BTW, the code to do this is quite simple:




import { ContentItem } from "screenpipe";
import { Client } from "npm:@notionhq/client";
import { z } from "zod";
import { generateObject } from "ai";
import { createOllama } from "ollama-ai-provider";
import { pipe } from "screenpipe";

const engineeringLog = z.object({
title: z.string(),
description: z.string(),
tags: z.array(z.string()),
});

type EngineeringLog = z.infer<typeof engineeringLog>;

async function generateEngineeringLog(
screenData: ContentItem[],
ollamaModel: string,
ollamaApiUrl: string
): Promise<EngineeringLog> {
const prompt = `Based on the following screen data, generate a concise engineering log entry:

${JSON.stringify(screenData)}

Focus only on engineering work. Ignore non-work related activities.
Return a JSON object with the following structure:
{
"title": "Brief title of the engineering task",
"description": "Concise description of the engineering work done",
"tags": ["tag1", "tag2", "tag3"]
}
Provide 1-3 relevant tags related to the engineering work.`
;

const provider = createOllama({ baseURL: ollamaApiUrl });

const response = await generateObject({
model: provider(ollamaModel),
messages: [{ role: "user", content: prompt }],
schema: engineeringLog,
});

console.log("ai answer:", response);

return response.object;
}

async function syncLogToNotion(
logEntry: EngineeringLog,
notion: Client,
databaseId: string
): Promise<void> {
try {
console.log("syncLogToNotion", logEntry);
await notion.pages.create({
parent: { database_id: databaseId },
properties: {
Title: { title: [{ text: { content: logEntry.title } }] },
Description: {
rich_text: [{ text: { content: logEntry.description } }],
},
Tags: { multi_select: logEntry.tags.map((tag) => ({ name: tag })) },
Date: { date: { start: new Date().toISOString() } },
},
});

console.log("engineering log synced to notion successfully");

// Create markdown table for inbox
const markdownTable = `
| Title | Description | Tags |
|-------|-------------|------|
|
${logEntry.title} | ${logEntry.description} | ${logEntry.tags.join(", ")} |
`
.trim();

await pipe.inbox.send({
title: "engineering log synced",
body: `new engineering log entry:\n\n${markdownTable}`,
});
} catch (error) {
console.error("error syncing engineering log to notion:", error);
await pipe.inbox.send({
title: "engineering log error",
body: `error syncing engineering log to notion: ${error}`,
});
}
}

function streamEngineeringLogsToNotion(): void {
console.log("starting engineering logs stream to notion");

const config = pipe.loadPipeConfig();
console.log("loaded config:", JSON.stringify(config, null, 2));

const interval = config.interval * 1000;
const databaseId = config.notionDatabaseId;
const apiKey = config.notionApiKey;
const ollamaApiUrl = config.ollamaApiUrl;
const ollamaModel = config.ollamaModel;

const notion = new Client({ auth: apiKey });

pipe.inbox.send({
title: "engineering log stream started",
body: `monitoring engineering work every ${config.interval} seconds`,
});

pipe.scheduler
.task("generateEngineeringLog")
.every(interval)
.do(async () => {
try {
const now = new Date();
const oneHourAgo = new Date(now.getTime() - interval);

const screenData = await pipe.queryScreenpipe({
startTime: oneHourAgo.toISOString(),
endTime: now.toISOString(),
limit: 50,
contentType: "ocr",
});

if (screenData && screenData.data.length > 0) {
const logEntry = await generateEngineeringLog(
screenData.data,
ollamaModel,
ollamaApiUrl
);
await syncLogToNotion(logEntry, notion, databaseId);
} else {
console.log("no relevant engineering work detected in the last hour");
}
} catch (error) {
console.error("error in engineering log pipeline:", error);
await pipe.inbox.send({
title: "engineering log error",
body: `error in engineering log pipeline: ${error}`,
});
}
});

pipe.scheduler.start();
}

streamEngineeringLogsToNotion();






Any ideas of other interesting plugins could be made?



Feel free to join our Discord!

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
SOC Incident Playbook: Remote Code Execution (RCE) Defense
title: Detect Exploitation - How to use Llama3.2 to write daily logs in Notion based on your screen
id: 326007f6-34a2-4fe1-bdce-95797a2b7f07
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "How to use Llama3.2 to write d" ascii wide
    condition:
        any of them
}
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich How to use Llama3.2 to write daily logs .... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten How to use Llama3.2 to write daily logs in Notion based on your screen

Thematisch verwandte Begriffe: Llama32, write, daily, logs · 6 Treffer

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-96891 | A vulnerability was identified in D-Link DIR-825 3.00b32. Affected is th…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel TTP ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick